From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 1/9] lib: stackprot: fix type for %pS
Date: Mon, 02 Jun 2025 13:57:38 +0200 [thread overview]
Message-ID: <174886545888.918949.7342295014365999538.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250527201359.889550-1-a.fatoum@pengutronix.de>
On Tue, 27 May 2025 22:13:51 +0200, Ahmad Fatoum wrote:
> Adding __printf to the panic definition in the follow up commit will
> make it evident that we are using a long value for a %pS format
> specifier, which is not correct, albeit they have the same size.
>
> Fix this by adding the missing cast.
>
>
> [...]
Applied, thanks!
[1/9] lib: stackprot: fix type for %pS
https://git.pengutronix.de/cgit/barebox/commit/?id=52596d188d6d (link may not be stable)
[2/9] fastboot: use correct format specifier for size_t
https://git.pengutronix.de/cgit/barebox/commit/?id=f3af60da5ed9 (link may not be stable)
[3/9] Makefile: don't warn over zero-size format string
https://git.pengutronix.de/cgit/barebox/commit/?id=e04094f4502c (link may not be stable)
[4/9] scripts: define __printf attribute macro
https://git.pengutronix.de/cgit/barebox/commit/?id=c828b74066bd (link may not be stable)
[5/9] treewide: specify __printf attribute directly on static definition
https://git.pengutronix.de/cgit/barebox/commit/?id=64a294ec1dea (link may not be stable)
[6/9] treewide: replace attribute with shorter __printf macro
https://git.pengutronix.de/cgit/barebox/commit/?id=a23e5d816124 (link may not be stable)
[7/9] treewide: add missing __printf attributes
https://git.pengutronix.de/cgit/barebox/commit/?id=b2adbadce5c6 (link may not be stable)
[8/9] vsprintf: add %ps format specifier for symbols without offset
https://git.pengutronix.de/cgit/barebox/commit/?id=71586b2b7869 (link may not be stable)
[9/9] lib: random: print get_crypto_bytes caller when no HWRNG is registered
https://git.pengutronix.de/cgit/barebox/commit/?id=2d309b83ccc2 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-06-02 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 20:13 Ahmad Fatoum
2025-05-27 20:13 ` [PATCH 2/9] fastboot: use correct format specifier for size_t Ahmad Fatoum
2025-05-27 20:13 ` [PATCH 3/9] Makefile: don't warn over zero-size format string Ahmad Fatoum
2025-05-27 20:13 ` [PATCH 4/9] scripts: define __printf attribute macro Ahmad Fatoum
2025-05-27 20:13 ` [PATCH 5/9] treewide: specify __printf attribute directly on static definition Ahmad Fatoum
2025-05-27 20:13 ` [PATCH 6/9] treewide: replace attribute with shorter __printf macro Ahmad Fatoum
2025-05-27 20:13 ` [PATCH 7/9] treewide: add missing __printf attributes Ahmad Fatoum
2025-05-27 20:13 ` [PATCH 8/9] vsprintf: add %ps format specifier for symbols without offset Ahmad Fatoum
2025-05-27 20:13 ` [PATCH 9/9] lib: random: print get_crypto_bytes caller when no HWRNG is registered Ahmad Fatoum
2025-06-02 11:57 ` 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=174886545888.918949.7342295014365999538.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