Standardise remaining uses of SDK to ESP-IDF

This commit is contained in:
Angus Gratton
2016-08-19 15:01:15 +08:00
parent fffba81bd3
commit 9ec0e1545d
13 changed files with 33 additions and 52 deletions
-5
View File
@@ -1,11 +1,6 @@
#
# Component Makefile
#
# This Makefile should, at the very least, just include $(SDK_PATH)/Makefile. By default,
# this will take the sources in this directory, compile them and link them into
# lib(subdirectory_name).a in the build directory. This behaviour is entirely configurable,
# please read the SDK documents if you need to do this.
#
COMPONENT_ADD_INCLUDEDIRS := include
+3 -3
View File
@@ -49,9 +49,9 @@ typedef enum {
/**
* @brief Open non-volatile storage with a given namespace
*
* Multiple SDK and application modules can store their key-value pairs in the
* NVS module. In order to reduce possible conflicts on key names, each module
* can use its own namespace.
* Multiple internal ESP-IDF and third party application modules can store
* their key-value pairs in the NVS module. In order to reduce possible
* conflicts on key names, each module can use its own namespace.
*
* @param[in] name Namespace name. Maximal length is determined by the
* underlying implementation, but is guaranteed to be