michaelh/zephyr
1
0
Fork 0
Code Releases Activity

kconfig: fixed Kconfig name in comments

Browse source 
Change-Id: Ia22e9df4b9d836635aef1d4b59efec8ce58815d6
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit is contained in:
Anas Nashif 2017-04-10 10:29:25 -04:00 • committed by Kumar Gala
commit 919b3f0878
2 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
include/debug/mem_safe.h
View file

@ -120,7 +120,7 @@ extern int _mem_safe_write_to_text_section(void *dest, char *buf,
* num_bytes. The read/write permissions are specified via @a perm and can * num_bytes. The read/write permissions are specified via @a perm and can
* take the values either SYS_MEM_SAFE_READ or SYS_MEM_SAFE_WRITE. * take the values either SYS_MEM_SAFE_READ or SYS_MEM_SAFE_WRITE.
* *
* The table size is specified via the CONFIG_MEM_SAFE_NUM_REGIONS kconfig * The table size is specified via the CONFIG_MEM_SAFE_NUM_EXTRA_REGIONS kconfig
* option. * option.
* *
* If the implementation of safe memory access chosen does not need this API, * If the implementation of safe memory access chosen does not need this API,

2
subsys/debug/Kconfig
View file

@ -33,7 +33,7 @@ config MEM_SAFE_CHECK_BOUNDARIES
Other regions can be added as needed by using the Other regions can be added as needed by using the
sys_mem_safe_region_add() API. The number of regions that can be added sys_mem_safe_region_add() API. The number of regions that can be added
is controlled via the MEM_SAFE_NUM_REGIONS kconfig option. is controlled via the MEM_SAFE_NUM_EXTRA_REGIONS kconfig option.
This implementation requires initialization and thus consumes some boot This implementation requires initialization and thus consumes some boot
time. time.