From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Eric Biggers" <ebiggers@kernel.org>,
"Ard Biesheuvel" <ardb+git@google.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, "Christoph Hellwig" <hch@lst.de>,
"Russell King" <linux@armlinux.org.uk>,
"Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [PATCH 0/2] ARM: Use type override hacks only in NEON code
Date: Fri, 18 Sep 2026 09:39:30 +0200 [thread overview]
Message-ID: <9e60a8ef-99aa-49f6-9332-53b70e307b5c@app.fastmail.com> (raw)
In-Reply-To: <20260918023054.GB1703@sol>
On Fri, 18 Sep 2026, at 04:30, Eric Biggers wrote:
> On Wed, Sep 09, 2026 at 06:33:20PM +0200, Ard Biesheuvel wrote:
>> From: Ard Biesheuvel <ardb@kernel.org>
>>
>> Now that the RAID-6 code can no longer be built for user space, we can
>> drop the direct dependency on the arm_neon.h system header, and include
>> asm/neon-intrinsics.h instead.
>>
>> Since asm/neon-intrinsics.h has all the type overrides needed to include
>> arm_neon.h without conflicts in the uintXX_t types, those hacks can be
>> dropped from asm/types.h, and so the file can be dropped entirely.
>>
>> Cc: Eric Biggers <ebiggers@kernel.org>
>> Cc: Christoph Hellwig <hch@lst.de>
>> Cc: Russell King <linux@armlinux.org.uk>
>> Cc: Arnd Bergmann <arnd@arndb.de>
>>
>> Ard Biesheuvel (2):
>> lib/raid6: Switch to Linux's NEON intrinsics header
>> ARM: Remove hacked-up asm/types.h header
>
> Reviewed-by: Eric Biggers <ebiggers@kernel.org>
>
Thanks.
I've dropped these into rmk's patch tracker.
prev parent reply other threads:[~2026-09-18 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 16:33 Ard Biesheuvel
2026-09-09 16:33 ` [PATCH 1/2] lib/raid6: Switch to Linux's NEON intrinsics header Ard Biesheuvel
2026-09-10 5:30 ` Christoph Hellwig
2026-09-09 16:33 ` [PATCH 2/2] ARM: Remove hacked-up asm/types.h header Ard Biesheuvel
2026-09-10 5:31 ` Christoph Hellwig
2026-09-18 2:30 ` [PATCH 0/2] ARM: Use type override hacks only in NEON code Eric Biggers
2026-09-18 7:39 ` 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=9e60a8ef-99aa-49f6-9332-53b70e307b5c@app.fastmail.com \
--to=ardb@kernel.org \
--cc=ardb+git@google.com \
--cc=arnd@arndb.de \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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
all inboxes | Powered by JetHome®