From: Tom Rini Date: Sun, 11 Oct 2020 21:14:40 -0400 Subject: [PATCH v2 1/2] log: Allow LOG_DEBUG to always enable log output In-Reply-To: <20200912171335.3889616-1-sjg@chromium.org> References: <20200912171335.3889616-1-sjg@chromium.org> Message-ID: <20201012011440.GL14816@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 Sat, Sep 12, 2020 at 11:13: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. > > With the new behaviour, log_debug() will always log if LOG_DEBUG is > enabled. > > Move log_test_syslog_nodebug() into its own file since it cannot be made > to work where it is, with LOG_DEBUG defined. > > Signed-off-by: Simon Glass Applied to u-boot/master, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: