helper: fix minor typos

Change-Id: I785e388148c0329e51cb0b39ab30e8ee44f5a7cd
Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
Reviewed-on: http://openocd.zylin.com/5801
Tested-by: jenkins
This commit is contained in:
Antonio Borneo 2020-07-12 00:57:34 +02:00
parent 60f104f450
commit aa628304e2
7 changed files with 13 additions and 13 deletions

View File

@ -4,7 +4,7 @@
echo "Usage: $0"
echo
echo "Read binary data from standard input and write it as a comma separated"
echo "list of hexadecimal byte values to standard ouput. The output is usable"
echo "list of hexadecimal byte values to standard output. The output is usable"
echo "as a C array initializer. It is terminated with a comma so it can be"
echo "continued e.g. for zero termination."
exit 1

View File

@ -168,7 +168,7 @@ struct command_invocation {
*
* This is *especially* important for commands such as writing
* to flash or verifying memory. The reason is that those commands
* can be used by programs to determine if the operation succeded
* can be used by programs to determine if the operation succeeded
* or not. If the operation failed, then a program can try
* an alternative approach.
*
@ -199,7 +199,7 @@ struct command {
* Commands should be registered by filling in one or more of these
* structures and passing them to [un]register_commands().
*
* A conventioal format should be used for help strings, to provide both
* A conventional format should be used for help strings, to provide both
* usage and basic information:
* @code
* "@<options@> ... - some explanation text"
@ -252,7 +252,7 @@ int register_commands(struct command_context *cmd_ctx, struct command *parent,
const struct command_registration *cmds);
/**
* Unregisters all commands from the specfied context.
* Unregisters all commands from the specified context.
* @param cmd_ctx The context that will be cleared of registered commands.
* @param parent If given, only clear commands from under this one command.
* @returns ERROR_OK on success, or an error code.
@ -265,7 +265,7 @@ struct command *command_find_in_context(struct command_context *cmd_ctx,
/**
* Update the private command data field for a command and all descendents.
* This is used when creating a new heirarchy of commands that depends
* This is used when creating a new hierarchy of commands that depends
* on obtaining a dynamically created context. The value will be available
* in command handlers by using the CMD_DATA macro.
* @param c The command (group) whose data pointer(s) will be updated.
@ -362,7 +362,7 @@ DECLARE_PARSE_WRAPPER(_target_addr, target_addr_t);
*
* This function may cause the calling function to return immediately,
* so it should be used carefully to avoid leaking resources. In most
* situations, parsing should be completed in full before proceding
* situations, parsing should be completed in full before proceeding
* to allocate resources, and this strategy will most prevents leaks.
*/
#define COMMAND_PARSE_NUMBER(type, in, out) \

View File

@ -127,7 +127,7 @@ void Jim_SetResult_NvpUnknown(Jim_Interp *interp,
/** Debug: convert argc/argv into a printable string for printf() debug
*
* \param interp - the interpeter
* \param interp - the interpreter
* \param argc - arg count
* \param argv - the objects
*
@ -150,7 +150,7 @@ const char *Jim_Debug_ArgvString(Jim_Interp *interp, int argc, Jim_Obj *const *a
* Some TCL objects have various "configuration" values.
* For example - in Tcl/Tk the "buttons" have many options.
*
* Usefull when dealing with command options.
* Useful when dealing with command options.
* that may come in any order...
*
* Does not support "-foo = 123" type options.

View File

@ -469,7 +469,7 @@ void kept_alive(void)
gdb_timeout_warning(delta_time);
}
/* if we sleep for extended periods of time, we must invoke keep_alive() intermittantly */
/* if we sleep for extended periods of time, we must invoke keep_alive() intermittently */
void alive_sleep(uint64_t ms)
{
uint64_t napTime = 10;
@ -493,7 +493,7 @@ void busy_sleep(uint64_t ms)
}
}
/* Maximum size of socket error message retreived from operation system */
/* Maximum size of socket error message retrieved from operation system */
#define MAX_SOCKET_ERR_MSG_LENGTH 256
/* Provide log message for the last socket error.

View File

@ -40,7 +40,7 @@
* LOG_LVL_SILENT - turn off all output. In lieu of try + catch this can be used as a
* feeble ersatz.
* LOG_LVL_USER - user messages. Could be anything from information
* to progress messags. These messages do not represent
* to progress messages. These messages do not represent
* incorrect or unexpected behaviour, just normal execution.
* LOG_LVL_ERROR - fatal errors, that are likely to cause program abort
* LOG_LVL_WARNING - non-fatal errors, that may be resolved later

View File

@ -6,7 +6,7 @@ use File::Basename;
if (@ARGV != 1) {
die "Usage: $0 <JEP106 PDF document>\n\n"
. "Convert the JEDEC document containing manufacturer identification codes\n"
. "to an array initializer suitable for incusion into jep106.c. The latest\n"
. "to an array initializer suitable for inclusion into jep106.c. The latest\n"
. "version of the document can be found here:\n"
. "http://www.jedec.org/standards-documents/results/jep106\n";
};

View File

@ -47,7 +47,7 @@ static const struct command_registration util_command_handlers[] = {
.mode = COMMAND_ANY,
.jim_handler = util_Jim_Command_ms,
.help =
"Returns ever increasing milliseconds. Used to calculuate differences in time.",
"Returns ever increasing milliseconds. Used to calculate differences in time.",
.usage = "",
},
COMMAND_REGISTRATION_DONE