From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: 9l@9lo.re
Subject: Re: [PATCH] include: linux/printk.h: allow forcing log level per file
Date: Mon, 09 Feb 2026 15:26:46 +0100 [thread overview]
Message-ID: <177064720624.672883.5804213845747463961.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260205171147.3096490-1-a.fatoum@pengutronix.de>
On Thu, 05 Feb 2026 18:11:43 +0100, Ahmad Fatoum wrote:
> We support defining DEBUG or VERBOSE_DEBUG to increase the log level per
> file, but we lack a way to decrease the log level.
>
> The latter could be useful when shotgun debugging with all debug logging
> enabled, as otherwise some debug output may drown out everything else.
>
> To support this, allow LOGLEVEL to be defined per file. We don't expect
> that any files committed to tree would do this, but it may turn out to
> be useful during debugging.
>
> [...]
Applied, thanks!
[1/1] include: linux/printk.h: allow forcing log level per file
https://git.pengutronix.de/cgit/barebox/commit/?id=c4657de3af99 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-02-09 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 17:11 Ahmad Fatoum
2026-02-09 14:26 ` Sascha Hauer [this message]
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=177064720624.672883.5804213845747463961.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=9l@9lo.re \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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