Trivial update to some comments and debug statement formats.

This commit is contained in:
Gregory Nutt 2018-07-14 07:08:51 -06:00
parent 0a4091b86a
commit 29474a2b08
2 changed files with 3 additions and 3 deletions

View File

@ -596,7 +596,7 @@ static const struct max3421e_usbhost_trace_s g_trace1[TRACE1_NSTRINGS] =
TRENTRY(MAX3421E_TRACE1_ASYNCHSETUP_FAIL1, TR_FMT1, "OUT: Asynch setup failed: %u\n"),
TRENTRY(MAX3421E_TRACE1_ASYNCHSETUP_FAIL2, TR_FMT1, "IN: Asynch setup failed: %u\n"),
#endif
TRENTRY(MAX3421E_TRACE1_BAD_JKSTATE, TR_FMT1, "StartSOF: Bad JK state: %02x\n"),
TRENTRY(MAX3421E_TRACE1_BAD_JKSTATE, TR_FMT1, "CONNECT: Bad JK state: %02x\n"),
TRENTRY(MAX3421E_TRACE1_BADREVISION, TR_FMT1, "INIT: Bad revision number: %02x\n"),
TRENTRY(MAX3421E_TRACE1_CHANALLOC_FAIL, TR_FMT1, "EPALLOC: Channel allocation failed: %u\n"),
TRENTRY(MAX3421E_TRACE1_CHANWAIT_FAIL, TR_FMT1, "OUT: Channel wait failure: %u\n"),

View File

@ -43,12 +43,12 @@ config EXECFUNCS_HAVE_SYMTAB
NOTE: This option only pre-initializes the system symbol table as
defined by CONFIG_EXECFUNCS_SYMTAB and CONFIG_EXECFUNCS_NSYMBOLS.
This is is simply an optional, automatic initialization of the
This is simply an optional, automatic initialization of the
system symbol table. You would need to do this, for example, in
in the kernel build were the first task must be run from a program
on the file system. This option has no other effect.
Optionally, you can always call binfmt_setsymtabl() from your
Optionally, you can always call binfmt_setsymtab() from your
board-specific logic or, equivalently, call boardctl(BOARDIOC_APP_SYMTAB)
from your application initialization logic.