From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH] log: Allow LOG_DEBUG to always enable log output
Date: Wed, 5 Aug 2020 08:18:19 -0400 [thread overview]
Message-ID: <20200805121819.GA24776@bill-the-cat> (raw)
In-Reply-To: <20200727022735.1435481-1-sjg@chromium.org>
On Sun, Jul 26, 2020 at 08:27:35PM -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@chromium.org>
This exposes an underlying problem with LOG and clang I believe:
https://gitlab.denx.de/u-boot/u-boot/-/jobs/135789
--
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/20200805/6eaf247d/attachment.sig>
next prev parent reply other threads:[~2020-08-05 12:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 2:27 [PATCH] log: Allow LOG_DEBUG to always enable log output Simon Glass
2020-07-27 6:15 ` Heinrich Schuchardt
2020-07-27 23:17 ` Simon Glass
2020-08-05 12:18 ` Tom Rini [this message]
2020-08-05 12:54 ` Heinrich Schuchardt
2020-08-05 12:56 ` Tom Rini
2020-08-05 18:31 ` Heinrich Schuchardt
2020-08-05 18:37 ` Tom Rini
2020-08-05 18:56 ` Simon Glass
2020-08-05 19:03 ` Tom Rini
2020-08-05 19:08 ` Heinrich Schuchardt
2020-08-05 19:32 ` Tom Rini
2020-09-28 4:24 ` Simon Glass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200805121819.GA24776@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox