From: Tom Rini <trini@konsulko.com>
To: Marek Vasut <marex@denx.de>
Cc: Christoph Niedermaier <cniedermaier@dh-electronics.com>,
u-boot@lists.denx.de,
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: Thu, 20 Mar 2025 07:53:04 -0600 [thread overview]
Message-ID: <20250320135304.GN2640854@bill-the-cat> (raw)
In-Reply-To: <a6ab86ac-4404-4081-8529-b8d11b37b5d2@denx.de>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
On Thu, Mar 20, 2025 at 12:49:17PM +0100, Marek Vasut wrote:
> On 3/20/25 11:23 AM, Christoph Niedermaier wrote:
> > If tiny printf is used with 0x%08X (upper case X) the output is
> > always 0x00000000. It could be confusing if upper case instead
> > of lower case is used intentionally or accidentally because the
> > actual value is not output. To avoid this confusion, tiny printf
> > is extended to support also the formatting with %X.
> >
> > Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com>
> TINY_PRINTF is meant to be tiny, i.e. not consume a lot of space, at the
> expense of functionality. This is meant to be used in size constrained
> environments, like the SPL. If you need full vsprintf() formatting support,
> disable TINY_PRINTF in your config and use the regular vsprintf()
> implementation.
Right. I could accept a patch to tiny-printf that treats %X like %x (so
that the value shown is correct) as that would be a minimal size change.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-03-20 13:53 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 [this message]
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
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=20250320135304.GN2640854@bill-the-cat \
--to=trini@konsulko.com \
--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=sjg@chromium.org \
--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