From: Conor Dooley <conor@kernel.org>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
Conor Dooley <conor.dooley@microchip.com>,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
wangyushan12@huawei.com
Subject: Re: [PATCH v1] arm64, lib: make ARM64 select ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION not GENERIC_CPU_CACHE_MAINTENANCE
Date: Fri, 21 Nov 2025 18:44:11 +0000 [thread overview]
Message-ID: <20251121-uncoated-trapeze-e1e7d9c0cbb8@spud> (raw)
In-Reply-To: <20251121104827.00005033@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 808 bytes --]
On Fri, Nov 21, 2025 at 10:48:27AM +0000, Jonathan Cameron wrote:
> On Thu, 20 Nov 2025 15:25:46 -0800
> Randy Dunlap <rdunlap@infradead.org> wrote:
> > On 11/20/25 1:40 PM, Catalin Marinas wrote:
> > > As an alternative, I'm happy for arm64 to select both the ARCH and
> > > GENERIC options if you think that works better.
> > >
> >
> > Yes, I think that would be much better.
> > Thanks.
> >
>
> I'm fine with that as well (was where we were in earlier versions).
> I'm offline for 10 days from tomorrow, but wangyushan +CC has been heavily
> involved in this series throughout if we need to test anything etc.
>
> For a patch that is basically just (this to me seems fine to squash
> as well if that is easier)
Right, 3 votes for both, so I squashed that in.
Thanks guys.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-11-21 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 19:08 [PATCH v1] arm64, lib: make ARM64 select ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION not GENERIC_CPU_CACHE_MAINTENANCE Conor Dooley
2025-11-19 21:22 ` Randy Dunlap
2025-11-20 17:30 ` Catalin Marinas
2025-11-20 19:29 ` Conor Dooley
2025-11-20 20:13 ` Randy Dunlap
2025-11-20 21:40 ` Catalin Marinas
2025-11-20 23:25 ` Randy Dunlap
2025-11-21 10:48 ` Jonathan Cameron
2025-11-21 18:44 ` Conor Dooley [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=20251121-uncoated-trapeze-e1e7d9c0cbb8@spud \
--to=conor@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=conor.dooley@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=wangyushan12@huawei.com \
--cc=will@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