From patchwork Tue May 26 09:48:02 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Patrick Delaunay X-Patchwork-Id: 246567 List-Id: U-Boot discussion From: patrick.delaunay at st.com (Patrick Delaunay) Date: Tue, 26 May 2020 11:48:02 +0200 Subject: [PATCH] doc: log: correct option name CONFIG_LOG_MAX_LEVEL Message-ID: <20200526094802.10927-1-patrick.delaunay@st.com> 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 --- doc/README.log | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/README.log b/doc/README.log index 1057981f45..170e4ba24e 100644 --- a/doc/README.log +++ b/doc/README.log @@ -60,13 +60,13 @@ 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 versions also, e.g. CONFIG_SPL_LOG_MAX_LEVEL. Temporary logging within a single file