kconfig: fixed Kconfig name in comments
Change-Id: Ia22e9df4b9d836635aef1d4b59efec8ce58815d6 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit is contained in:
parent
3738d0de24
commit
919b3f0878
2 changed files with 2 additions and 2 deletions
|
@ -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
|
||||
* 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.
|
||||
*
|
||||
* If the implementation of safe memory access chosen does not need this API,
|
||||
|
|
|
@ -33,7 +33,7 @@ config MEM_SAFE_CHECK_BOUNDARIES
|
|||
|
||||
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.
|
||||
is controlled via the MEM_SAFE_NUM_EXTRA_REGIONS kconfig option.
|
||||
|
||||
This implementation requires initialization and thus consumes some boot
|
||||
time.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue