From: Nathan Chancellor <nathan@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-kbuild@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Eric Biggers <ebiggers@kernel.org>
Subject: Re: [PATCH 0/4] Get rid of all NEON intrinsics stdint.h type hacks
Date: Fri, 13 Nov 2026 12:01:50 -0700 [thread overview]
Message-ID: <20261113190150.GA2857474@ax162> (raw)
In-Reply-To: <bc58b973-3d54-4480-aaaa-f5d5269418ea@app.fastmail.com>
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.
--
Cheers,
Nathan
next prev parent reply other threads:[~2026-11-13 19:02 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 [this message]
2026-11-13 20:05 ` Ard Biesheuvel
2026-11-13 20:30 ` Eric Biggers
2026-11-13 21:47 ` Ard Biesheuvel
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=20261113190150.GA2857474@ax162 \
--to=nathan@kernel.org \
--cc=ardb@kernel.org \
--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 \
/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