From: Tom Rini Date: Sun, 11 Oct 2020 21:15:29 -0400 Subject: [PATCH v2] log: Allow LOG_DEBUG to always enable log output In-Reply-To: <20200927155534.1560321-1-sjg@chromium.org> References: <20200927155534.1560321-1-sjg@chromium.org> Message-ID: <20201012011529.GU14816@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Sun, Sep 27, 2020 at 09:55:34AM -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 > --- > > Changes in v2: > - Avoid clang-10 warning about converting an enum constant to a boolean So, this is v2 and https://patchwork.ozlabs.org/project/uboot/patch/20200912171335.3889616-1-sjg at chromium.org/ is also v2, and I started by taking the former. It looks like that might be right but please send a follow-up to reconcile anything that needs it, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: