From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 1/4] printf: define printk/no_printk in terms of prints
Date: Mon, 01 Dec 2025 11:22:01 +0100 [thread overview]
Message-ID: <176458452181.161296.7515277119174354375.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20251128125616.136559-1-a.fatoum@pengutronix.de>
On Fri, 28 Nov 2025 13:50:02 +0100, Ahmad Fatoum wrote:
> We will later move printk into its own header while giving it more
> Linux-like semantics. Prepare for that by defining no_printf, so users
> across the tree can make use of it without including <linux/printk.h>.
>
>
Applied, thanks!
[1/4] printf: define printk/no_printk in terms of prints
https://git.pengutronix.de/cgit/barebox/commit/?id=814452f6e072 (link may not be stable)
[2/4] bug: add support for CONFIG_DEBUG_BUGVERBOSE
https://git.pengutronix.de/cgit/barebox/commit/?id=10536edcc3bf (link may not be stable)
[3/4] include: move sprintf prototypes to new linux/sprintf.h
https://git.pengutronix.de/cgit/barebox/commit/?id=8862958f8071 (link may not be stable)
[4/4] console: move non-stdio elements to console.h
https://git.pengutronix.de/cgit/barebox/commit/?id=6550746b5a87 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-12-01 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 12:50 Ahmad Fatoum
2025-11-28 12:50 ` [PATCH 2/4] bug: add support for CONFIG_DEBUG_BUGVERBOSE Ahmad Fatoum
2025-11-28 12:50 ` [PATCH 3/4] include: move sprintf prototypes to new linux/sprintf.h Ahmad Fatoum
2025-11-28 12:50 ` [PATCH 4/4] console: move non-stdio elements to console.h Ahmad Fatoum
2025-12-01 10:22 ` 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=176458452181.161296.7515277119174354375.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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