Linux cryptographic layer development
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Catalin Marinas" <catalin.marinas@arm.com>,
	linux-kbuild@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-crypto@vger.kernel.org,
	"Ard Biesheuvel" <ardb+git@google.com>
Cc: "Will Deacon" <will@kernel.org>, "Christoph Hellwig" <hch@lst.de>,
	"Eric Biggers" <ebiggers@kernel.org>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Song Liu" <song@kernel.org>, "Yu Kuai" <yukuai@fygo.io>
Subject: Re: (subset) [PATCH 0/4] Get rid of all NEON intrinsics stdint.h type hacks
Date: Thu, 19 Nov 2026 13:08:51 +0100	[thread overview]
Message-ID: <81ddf2f1-faec-47ec-b3b1-7210b4e7712b@app.fastmail.com> (raw)
In-Reply-To: <179508547602.2557572.9682726373932810888.b4-ty@b4>



On Thu, 19 Nov 2026, at 11:51, Catalin Marinas wrote:
> On Thu, 29 Oct 2026 14:50:20 +0100, Ard Biesheuvel wrote:
>> Recent Clang has become more finicky when it comes to overriding the
>> type macros that the freestanding stdint.h consumes when defining the
>> uintXX_t types, and so it is time to finally get rid of this entirely.
>> 
>> So instead of making stdint.h (which comes from the compiler when
>> -ffreestanding is set on the command line) agree with the kernel's
>> linux/types.h header, avoid the latter entirely in the compilation units
>> that actually use the NEON intrinsics (which are always leaf functions
>> that are not tightly coupled to kernel APIs).
>> 
>> [...]
>
> Applied the first three patches to arm64 (for-next/fixes), thanks! I
> also added a cc stable, though it won't be a straightforward
> cherry-pick.

Thanks!


> I left the last patch out, IIUC it's just clean-up rather
> than fixing a problem on arm32 and can go separately via Russell's tree
> during the next merge window (let me know if you think otherwise).
>

I'll let Nathan respond to that.



  reply	other threads:[~2026-11-19 12:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 13:50 [PATCH 0/4] Get rid of all NEON intrinsics stdint.h type hacks Ard Biesheuvel
2026-10-29 13:50 ` [PATCH 1/4] lib/crc: Don't include <linux/types.h> in NEON intrinsics code Ard Biesheuvel
2026-11-13  9:03   ` Thomas Huth
2026-10-29 13:50 ` [PATCH 2/4] xor: arm/arm64: Move NEON xor_gen() dispatch into the glue code Ard Biesheuvel
2026-10-29 13:50 ` [PATCH 3/4] arm64: Drop stdint.h type overrides from asm/neon-intrinsics.h Ard Biesheuvel
2026-10-29 13:50 ` [PATCH 4/4] ARM: " Ard Biesheuvel
2026-10-29 21:41 ` [PATCH 0/4] Get rid of all NEON intrinsics stdint.h type hacks Nathan Chancellor
2026-11-01 22:00 ` Eric Biggers
2026-11-12 22:27 ` Nathan Chancellor
2026-11-13  8:23   ` Ard Biesheuvel
2026-11-13 19:01     ` Nathan Chancellor
2026-11-13 20:05       ` Ard Biesheuvel
2026-11-13 20:30         ` Eric Biggers
2026-11-13 21:47           ` Ard Biesheuvel
2026-11-19 10:51 ` (subset) " Catalin Marinas
2026-11-19 12:08   ` Ard Biesheuvel [this message]
2026-11-19 19:28     ` Nathan Chancellor

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=81ddf2f1-faec-47ec-b3b1-7210b4e7712b@app.fastmail.com \
    --to=ardb@kernel.org \
    --cc=ardb+git@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=ebiggers@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=song@kernel.org \
    --cc=will@kernel.org \
    --cc=yukuai@fygo.io \
    /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