From: Rasmus Villemoes <ravi@prevas.dk>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 0/3] integer limit macro consolidation
Date: Mon, 07 Jul 2025 22:39:14 +0200 [thread overview]
Message-ID: <87ecurwxal.fsf@prevas.dk> (raw)
In-Reply-To: <20250704221033.GN6424@bill-the-cat> (Tom Rini's message of "Fri, 4 Jul 2025 16:10:33 -0600")
On Fri, Jul 04 2025, Tom Rini <trini@konsulko.com> wrote:
> On Thu, Jul 03, 2025 at 01:37:27PM +0200, Rasmus Villemoes wrote:
>
>> I was bitten by our limit macros not being usable in #if conditionals
>> when building a standalone app. It turns out that the work to fix that
>> had already been started by the inclusion of the mbedtls library, so
>> it's something that people do hit.
>>
>> Let's finish the job by providing suitable limit macros for all three families:
>>
>> - Standard C types, char, short, ...
>> - Kernel-style fixed-width types s8, u64, ...
>> - POSIX/C99 fixed-width types int16_t, uint32_t, ...
>>
>
> Thanks for doing this. I assume you put this through CI?
I wanted to, forgot to actually do it. But now I have, and it found a
thinko/typo in 1/3. Fixed that up and now CI is happy, so just sent v2.
Thanks,
Rasmus
prev parent reply other threads:[~2025-07-07 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 11:37 [PATCH 0/3] integer limit macro consolidation Rasmus Villemoes
2025-07-03 11:37 ` [PATCH 1/3] move more limits from kernel.h to limits.h and standardize their definitions Rasmus Villemoes
2025-07-03 11:37 ` [PATCH 2/3] move limits for sNN/uNN types from kernel.h to limits.h Rasmus Villemoes
2025-07-03 11:37 ` [PATCH 3/3] limits.h: provide all limit macros for standard [u]intNN_t types Rasmus Villemoes
2025-07-04 22:10 ` [PATCH 0/3] integer limit macro consolidation Tom Rini
2025-07-07 20:39 ` Rasmus Villemoes [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=87ecurwxal.fsf@prevas.dk \
--to=ravi@prevas.dk \
--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