[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YVY15nd56j8x8udh@kernel.org>
Date: Thu, 30 Sep 2021 15:10:46 -0700
From: Mike Rapoport <rppt@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Juergen Gross <jgross@...e.com>,
Mike Rapoport <rppt@...ux.ibm.com>,
Shahab Vahedi <Shahab.Vahedi@...opsys.com>,
devicetree <devicetree@...r.kernel.org>,
iommu <iommu@...ts.linux-foundation.org>,
kasan-dev <kasan-dev@...glegroups.com>,
KVM list <kvm@...r.kernel.org>,
alpha <linux-alpha@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-efi <linux-efi@...r.kernel.org>,
"open list:BROADCOM NVRAM DRIVER" <linux-mips@...r.kernel.org>,
Linux-MM <linux-mm@...ck.org>,
linux-riscv <linux-riscv@...ts.infradead.org>,
linux-s390 <linux-s390@...r.kernel.org>,
Linux-sh list <linux-sh@...r.kernel.org>,
"open list:SYNOPSYS ARC ARCHITECTURE"
<linux-snps-arc@...ts.infradead.org>,
linux-um <linux-um@...ts.infradead.org>,
linux-usb@...r.kernel.org,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
linux-sparc <sparclinux@...r.kernel.org>,
xen-devel@...ts.xenproject.org
Subject: Re: [PATCH v2 0/6] memblock: cleanup memblock_free interface
On Thu, Sep 30, 2021 at 02:20:33PM -0700, Linus Torvalds wrote:
> On Thu, Sep 30, 2021 at 11:50 AM Mike Rapoport <rppt@...nel.org> wrote:
> >
> > The first patch is a cleanup of numa_distance allocation in arch_numa I've
> > spotted during the conversion.
> > The second patch is a fix for Xen memory freeing on some of the error
> > paths.
>
> Well, at least patch 2 looks like something that should go into 5.15
> and be marked for stable.
>
> Patch 1 looks like a trivial local cleanup, and could go in
> immediately. Patch 4 might be in that same category.
>
> The rest look like "next merge window" to me, since they are spread
> out and neither bugfixes nor tiny localized cleanups (iow renaming
> functions, global resulting search-and-replace things).
>
> So my gut feel is that two (maybe three) of these patches should go in
> asap, with three (maybe four) be left for 5.16.
>
> IOW, not trat this as a single series.
>
> Hmm?
Yes, why not :)
I'd keep patch 4 for the next merge window, does not look urgent to me.
Andrew, can you please take care of this or you'd prefer me resending
everything separately?
> Linus
--
Sincerely yours,
Mike.
Powered by blists - more mailing lists