Message ID | 20200527074331.4607-1-patrick.delaunay@st.com |
---|---|
State | Accepted |
Commit | b44c751efe09e0069ba4ca6fca246b935bf5efcc |
Headers | show |
Series | [v2] doc: log: correct option name CONFIG_LOG_MAX_LEVEL | expand |
On Wed, 27 May 2020 at 01:43, Patrick Delaunay <patrick.delaunay at st.com> wrote: > > Replace CONFIG_(SPL_)MAX_LOG_LEVEL by the correct name as defined in > common/Kconfig: > line 668:config LOG_MAX_LEVEL > line 688:config SPL_LOG_MAX_LEVEL > line 708:config TPL_LOG_MAX_LEVEL > > Signed-off-by: Patrick Delaunay <patrick.delaunay at st.com> > --- > > Changes in v2: > - add commnet for TPL with CONFIG_TPL_LOG_MAX_LEVEL example > > doc/README.log | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) Reviewed-by: Simon Glass <sjg at chromium.org>
diff --git a/doc/README.log b/doc/README.log index 1057981f45..ba838824a9 100644 --- a/doc/README.log +++ b/doc/README.log @@ -60,13 +60,14 @@ Enabling logging The following options are used to enable logging at compile time: CONFIG_LOG - Enables the logging system - CONFIG_MAX_LOG_LEVEL - Max log level to build (anything higher is compiled + CONFIG_LOG_MAX_LEVEL - Max log level to build (anything higher is compiled out) CONFIG_LOG_CONSOLE - Enable writing log records to the console If CONFIG_LOG is not set, then no logging will be available. -The above have SPL versions also, e.g. CONFIG_SPL_MAX_LOG_LEVEL. +The above have SPL and TPL versions also, e.g. CONFIG_SPL_LOG_MAX_LEVEL and +CONFIG_TPL_LOG_MAX_LEVEL. Temporary logging within a single file
Replace CONFIG_(SPL_)MAX_LOG_LEVEL by the correct name as defined in common/Kconfig: line 668:config LOG_MAX_LEVEL line 688:config SPL_LOG_MAX_LEVEL line 708:config TPL_LOG_MAX_LEVEL Signed-off-by: Patrick Delaunay <patrick.delaunay at st.com> --- Changes in v2: - add commnet for TPL with CONFIG_TPL_LOG_MAX_LEVEL example doc/README.log | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)