From: "Michael Walle" <mwalle@kernel.org>
To: "Quentin Schulz" <quentin.schulz@cherry.de>,
"Marek Vasut" <marex@denx.de>,
"Christoph Niedermaier" <cniedermaier@dh-electronics.com>,
<u-boot@lists.denx.de>
Cc: "Tom Rini" <trini@konsulko.com>,
"Benedikt Spranger" <b.spranger@linutronix.de>,
"Simon Glass" <sjg@chromium.org>,
"John Ogness" <john.ogness@linutronix.de>,
"Jerome Forissier" <jerome.forissier@linaro.org>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH] tiny-printf: Add support for upper case hex values
Date: Tue, 01 Apr 2025 10:55:42 +0200 [thread overview]
Message-ID: <D8V6D9S6CBRH.3LRHNU4XCVF14@kernel.org> (raw)
In-Reply-To: <ab32ace5-efc0-41b9-8d13-292f6f87835d@cherry.de>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Hi,
> The issue is that disabling TINY_PRINTF may not be possible (size
> constraints) and some code is compiled for different stages and people
> typically don't check whether the format used in printf is valid with
> tiny_printf. I've had this issue already in the past, I vaguely recall
> "complaining" about it on IRC.
Yes, I've stumbled on "%pa" with tiny printf (i.e. in
drivers/pinctrl/pinctrl-single.c) which is printing the very wrong
value, actually :) So printing anything unknown as '?' would really
help here.
-michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
next prev parent reply other threads:[~2025-04-01 8:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 10:23 [PATCH] tiny-printf: Add support for upper case hex values Christoph Niedermaier
2025-03-20 11:49 ` Marek Vasut
2025-03-20 13:53 ` Tom Rini
2025-03-20 14:00 ` Quentin Schulz
2025-03-20 14:14 ` Marek Vasut
2025-03-20 14:18 ` Tom Rini
2025-03-20 17:58 ` Christoph Niedermaier
2025-03-20 18:28 ` Tom Rini
2025-03-20 18:41 ` Christoph Niedermaier
2025-04-01 8:55 ` Michael Walle [this message]
2025-04-01 14:08 ` Christoph Niedermaier
2025-04-02 7:01 ` Michael Walle
2025-04-02 9:03 ` Christoph Niedermaier
2025-04-04 8:33 ` Michael Walle
2025-04-04 14:58 ` Tom Rini
2025-04-07 5:27 ` Michael Walle
2025-04-07 6:55 ` Christoph Niedermaier
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=D8V6D9S6CBRH.3LRHNU4XCVF14@kernel.org \
--to=mwalle@kernel.org \
--cc=b.spranger@linutronix.de \
--cc=cniedermaier@dh-electronics.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jerome.forissier@linaro.org \
--cc=john.ogness@linutronix.de \
--cc=marex@denx.de \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--cc=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