diff options
| author | Benjamin Walsh <benjamin.walsh@windriver.com> | 2016-04-11 17:18:44 -0400 |
|---|---|---|
| committer | Anas Nashif <nashif@linux.intel.com> | 2016-04-16 05:29:21 +0000 |
| commit | 6ec02cc80758e36fc15d4263c95eb3e84da8bcc5 (patch) | |
| tree | 1ecc573128de3bdbe520e98ad851b9cd11f5d96e /misc | |
| parent | f557d71b52adc4a3f2742fed6c52aef95658490f (diff) | |
debug: fit Kconfig lines in 80 columns
Change-Id: I2df06d14cf0c219006adf7609542498b78ce342e
Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
Diffstat (limited to 'misc')
| -rw-r--r-- | misc/debug/Kconfig | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/misc/debug/Kconfig b/misc/debug/Kconfig index 51a3d3ff4..093f9b64a 100644 --- a/misc/debug/Kconfig +++ b/misc/debug/Kconfig @@ -24,9 +24,9 @@ config MEM_SAFE prompt "Enable safe memory access" default n help - Add the routines available in mem_safe.h to the system. This is added as a - kconfig option instead of simply linking against the library because some - implementations might require initialization. + Add the routines available in mem_safe.h to the system. This is added + as a kconfig option instead of simply linking against the library + because some implementations might require initialization. choice prompt "Safe memory access implementation" @@ -36,13 +36,13 @@ config MEM_SAFE_CHECK_BOUNDARIES bool prompt "Software validation of memory access within memory regions" help - This implementation checks the application image's text/rodata boundaries - for its read-only region and the data/bss/noinit boundaries for its - read-write region, in software. + This implementation checks the application image's text/rodata + boundaries for its read-only region and the data/bss/noinit boundaries + for its read-write region, in software. - Other regions can be added as needed by using the sys_mem_safe_region_add() - API. The number of regions that can be added is controlled via the - MEM_SAFE_NUM_REGIONS kconfig option. + Other regions can be added as needed by using the + sys_mem_safe_region_add() API. The number of regions that can be added + is controlled via the MEM_SAFE_NUM_REGIONS kconfig option. This implementation requires initialization and thus consumes some boot time. @@ -51,14 +51,14 @@ endchoice config MEM_SAFE_NUM_EXTRA_REGIONS int - prompt "Number of safe memory access regions that can be added at runtime" + prompt "Number of safe memory access regions to be added at runtime" depends on MEM_SAFE_CHECK_BOUNDARIES default 0 help - The functions available in mem_safe.h check if memory is within read-only - or read-write regions before accessing it instead of crashing. The kernel - image is added as a valid region automatically, but other regions can be - added if the application makes access to additional memory outside of the - image's boundaries. + The functions available in mem_safe.h check if memory is within + read-only or read-write regions before accessing it instead of crashing. + The kernel image is added as a valid region automatically, but other + regions can be added if the application makes access to additional + memory outside of the image's boundaries. endmenu |