public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
* [PATCH v2] doc: log: correct option name CONFIG_LOG_MAX_LEVEL
@ 2020-05-27  7:43 Patrick Delaunay
  2020-05-31 14:08 ` Simon Glass
  0 siblings, 1 reply; 3+ messages in thread
From: Patrick Delaunay @ 2020-05-27  7:43 UTC (permalink / raw)
  To: u-boot

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@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(-)

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
-- 
2.17.1

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* [PATCH v2] doc: log: correct option name CONFIG_LOG_MAX_LEVEL
  2020-05-27  7:43 [PATCH v2] doc: log: correct option name CONFIG_LOG_MAX_LEVEL Patrick Delaunay
@ 2020-05-31 14:08 ` Simon Glass
  2020-06-13  3:11   ` sjg at google.com
  0 siblings, 1 reply; 3+ messages in thread
From: Simon Glass @ 2020-05-31 14:08 UTC (permalink / raw)
  To: u-boot

On Wed, 27 May 2020 at 01:43, Patrick Delaunay <patrick.delaunay@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@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@chromium.org>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [PATCH v2] doc: log: correct option name CONFIG_LOG_MAX_LEVEL
  2020-05-31 14:08 ` Simon Glass
@ 2020-06-13  3:11   ` sjg at google.com
  0 siblings, 0 replies; 3+ messages in thread
From: sjg at google.com @ 2020-06-13  3:11 UTC (permalink / raw)
  To: u-boot

On Wed, 27 May 2020 at 01:43, Patrick Delaunay <patrick.delaunay@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@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@chromium.org>

Applied to u-boot-dm, thanks!

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-06-13  3:11 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-05-27  7:43 [PATCH v2] doc: log: correct option name CONFIG_LOG_MAX_LEVEL Patrick Delaunay
2020-05-31 14:08 ` Simon Glass
2020-06-13  3:11   ` sjg at google.com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox