Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Eric Biggers" <ebiggers@kernel.org>,
	"Catalin Marinas" <catalin.marinas@arm.com>
Cc: "Nathan Chancellor" <nathan@kernel.org>,
	linux-kbuild@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-crypto@vger.kernel.org, "Christoph Hellwig" <hch@lst.de>
Subject: Re: [PATCH 0/4] Get rid of all NEON intrinsics stdint.h type hacks
Date: Fri, 13 Nov 2026 22:47:06 +0100	[thread overview]
Message-ID: <289380e8-9bdd-4769-b62e-dbedb553a16e@app.fastmail.com> (raw)
In-Reply-To: <20261113203007.GB29151@quark>

cc Catalin for real this time.

TL;DR Clang builds are broken due to type override hacks that we
don't actually need.

Please consider these for the arm64 tree, preferably as fixes.

On Fri, 13 Nov 2026, at 21:30, Eric Biggers wrote:
> On Fri, Nov 13, 2026 at 09:05:32PM +0100, Ard Biesheuvel wrote:
>> (cc Catalin)
>> 
>> Full thread:
>> https://lore.kernel.org/all/20261029135020.272082-6-ardb+git@google.com/
>> 
>> On Fri, 13 Nov 2026, at 20:01, Nathan Chancellor wrote:
>> > On Fri, Nov 13, 2026 at 09:23:03AM +0100, Ard Biesheuvel wrote:
>> >> On Thu, 12 Nov 2026, at 23:27, Nathan Chancellor wrote:
>> >> > Who do you think should take this series? It would be nice if it could
>> >> > start making its way to mainline sooner rather than later since tip of
>> >> > tree clang builds have been broken for over a month at this point.
>> >> >
>> >> 
>> >> Are the first two patches sufficient for that? Perhaps Eric can take them
>> >> through the CRC or libcrypto trees, and I can send the remaining ones
>> >> through the respective arch trees the following cycle.
>> >
>> > Unfortunately not :/ we need the third patch to resolve the error since
>> > that is where the conflict is originating.
>> >
>> 
>> OK in that case, maybe Catalin can take the whole thing via the arm64 tree? 
>> 
>> 
>> 
>> Diffstat:
>> 
>> Ard Biesheuvel (4):
>>   lib/crc: Don't include <linux/types.h> in NEON intrinsics code
>>   xor: arm/arm64: Move NEON xor_gen() dispatch into the glue code
>>   arm64: Drop stdint.h type overrides from asm/neon-intrinsics.h
>>   ARM: Drop stdint.h type overrides from asm/neon-intrinsics.h
>> 
>>  Documentation/arch/arm/kernel_mode_neon.rst | 10 +++--
>>  arch/arm/include/asm/neon-intrinsics.h      | 43 +++-----------------
>>  arch/arm64/include/asm/neon-intrinsics.h    | 24 +++--------
>>  lib/crc/crc64-neon.c                        | 10 ++---
>>  lib/raid/xor/arm/xor-neon-glue.c            |  3 ++
>>  lib/raid/xor/arm/xor-neon.h                 | 16 +++++++-
>>  lib/raid/xor/arm64/xor-eor3.c               | 15 ++-----
>>  lib/raid/xor/arm64/xor-neon-glue.c          |  5 +++
>>  lib/raid/xor/arm64/xor-neon.h               | 31 ++++++++++++--
>>  lib/raid/xor/xor-neon.c                     | 16 ++------
>>  10 files changed, 78 insertions(+), 95 deletions(-)
>
> I agree the arm64 tree makes the most sense for cross-subsystem arm and
> arm64 infrastructure changes like this.
>
> - Eric


      reply	other threads:[~2026-11-13 21:47 UTC|newest]

Thread overview: 14+ 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 [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=289380e8-9bdd-4769-b62e-dbedb553a16e@app.fastmail.com \
    --to=ardb@kernel.org \
    --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 \
    /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