[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20260116144431.f597298658fbfe5931e15cab@linux-foundation.org>
Date: Fri, 16 Jan 2026 14:44:31 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Liam R. Howlett" <Liam.Howlett@...cle.com>
Cc: kernel test robot <lkp@...el.com>, oe-kbuild-all@...ts.linux.dev, Linux
Memory Management List <linux-mm@...ck.org>,
maple-tree@...ts.infradead.org, linux-kernel@...r.kernel.org, Suren
Baghdasaryan <surenb@...gle.com>, Matthew Wilcox <willy@...radead.org>,
Sidhartha Kumar <sidhartha.kumar@...cle.com>, Vlastimil Babka
<vbabka@...e.cz>, Alice Ryhl <aliceryhl@...gle.com>, Kuninori Morimoto
<kuninori.morimoto.gx@...esas.com>, Geert Uytterhoeven
<geert@...ux-m68k.org>, Arnd Bergmann <arnd@...db.de>, Christian Kujau
<lists@...dbynature.de>
Subject: Re: [PATCH 16/28] maple_tree: Start using maple copy node for
destination
On Fri, 16 Jan 2026 15:19:30 -0500 "Liam R. Howlett" <Liam.Howlett@...cle.com> wrote:
> Fixing these in patch 16 means that future patches will need fixing.
>
> I can either send you patches to fix up this and subsequent patches. It
> might be better for me to respin the series?
>
> Let me know what you think I should do here.
>
> I'll also include a final patch to correct any other sparse warnings.
Regardless of the From:, a tremendously huge v1 patchset against critical
infrastructure at -rc5 got instaparked in my wait-and-see bucket, sorry ;)
A full resend would suit, thanks.
Powered by blists - more mailing lists