[PATCH 1/3] log: Allow LOG_DEBUG to always enable log output

Tom Rini trini at konsulko.com
Fri May 15 20:47:21 CEST 2020


On Wed, May 06, 2020 at 08:03:55AM -0600, Simon Glass wrote:

> At present if CONFIG_LOG enabled, putting LOG_DEBUG at the top of a file
> (before log.h inclusion) causes _log() to be executed for every log()
> call, regardless of the build- or run-time logging level.
> 
> However there is no guarantee that the log record will actually be
> displayed. If the current log level is lower than LOGL_DEBUG then it will
> not be.
> 
> Add a way to signal that the log record should always be displayed and
> update log_passes_filters() to handle this.
> 
> Signed-off-by: Simon Glass <sjg at chromium.org>
> ---
> 
>  common/log.c   |  6 +++++-
>  doc/README.log |  7 ++-----
>  include/log.h  | 16 ++++++++++++----
>  3 files changed, 19 insertions(+), 10 deletions(-)

Two levels of problems with (I believe) this patch:
https://gitlab.denx.de/u-boot/u-boot/-/jobs/94674 fails a unit test now
around logging.
https://gitlab.denx.de/u-boot/u-boot/-/jobs/94671 shows a ton of new
warnings with clang.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200515/8bdd46a5/attachment.sig>


More information about the U-Boot mailing list