Re: [PATCH RFC 00/18] arch, mm: create a generic set_memory/change_page_attr core
Mike Rapoport <[email protected]>
| Newsgroups | org.infradead.lists.linux-riscv,dev.linux.lists.loongarch,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-kernel,org.kvack.linux-mm |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Jul 22, 2026 at 10:03:03AM -0700, Dave Hansen wrote: > On 7/21/26 10:19, Borislav Petkov wrote: > > On Tue, Jul 21, 2026 at 07:23:23PM +0300, Mike Rapoport (Microsoft) wrote: > >> Currently there are 6 independent implementations for set_memory and > >> set_direct_map APIs. > > So with all mm/x86/CPA patches flying around, can we first agree on which tree > > is going to collect everything? > > > > And if I want to review patches in that area, what am I applying it ontop? > > linux-next perhaps... > > > > Let's sort out the workflow first so that we don't get lost on fruitless bug > > chases and fingerpointing. > > Just practically, I think this series needs to be ignored for a bit. Bug > fixes first, features and cleanups second. Ignored is a bit strong, I'd still love to get feedback on the concept. > When the time is right, it probably needs to get get acks from all the > affected architectures and go through mm. Folks can ack it now, but I > don't think anyone should even consider merging it until ~7.3-rc1. FWIF, I didn't plan to send non-RFC version before 7.3-rc1. -- Sincerely yours, Mike. _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv