Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	linux-kbuild@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-crypto@vger.kernel.org,
	Ard Biesheuvel <ardb+git@google.com>,
	Will Deacon <will@kernel.org>, Christoph Hellwig <hch@lst.de>,
	Eric Biggers <ebiggers@kernel.org>, Song Liu <song@kernel.org>,
	Yu Kuai <yukuai@fygo.io>, Russell King <linux@armlinux.org.uk>
Subject: Re: (subset) [PATCH 0/4] Get rid of all NEON intrinsics stdint.h type hacks
Date: Fri, 20 Nov 2026 10:08:54 +0000	[thread overview]
Message-ID: <awAcNlbDwM6xmLjH@arm.com> (raw)
In-Reply-To: <20261119192848.GB875856@ax162>

On Thu, Nov 19, 2026 at 12:28:48PM -0700, Nathan Chancellor wrote:
> On Thu, Nov 19, 2026 at 01:08:51PM +0100, Ard Biesheuvel wrote:
> > On Thu, 19 Nov 2026, at 11:51, Catalin Marinas wrote:
> > > 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.
> 
> Yeah, as far as I am aware, we only need the arm64 bits. arm builds are
> fine right now. Russell's tree would need to have the first two patches
> to apply the arm change if I understand correctly so it could either go
> to 7.5 with a backmerge or 7.6 with a base of 7.5-rc1.

I plan to send the first three patches as fixes for -rc, so they'll be
in 7.4. Russell can merge the other one for 7.5-rcX (well, Ard still
needs to cc him; copied now).

-- 
Catalin

      reply	other threads:[~2026-11-20 10:08 UTC|newest]

Thread overview: 18+ 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
2026-11-19 19:28     ` Nathan Chancellor
2026-11-20 10:08       ` Catalin Marinas [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=awAcNlbDwM6xmLjH@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=ardb+git@google.com \
    --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 \
    --cc=linux@armlinux.org.uk \
    --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