[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250205235219.3c3a4b968087d1386d708b04@linux-foundation.org>
Date: Wed, 5 Feb 2025 23:52:19 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Ryan Roberts <ryan.roberts@....com>
Cc: Catalin Marinas <catalin.marinas@....com>, Will Deacon
<will@...nel.org>, Muchun Song <muchun.song@...ux.dev>, Pasha Tatashin
<pasha.tatashin@...een.com>, Uladzislau Rezki <urezki@...il.com>, Christoph
Hellwig <hch@...radead.org>, Mark Rutland <mark.rutland@....com>, Ard
Biesheuvel <ardb@...nel.org>, Anshuman Khandual
<anshuman.khandual@....com>, Dev Jain <dev.jain@....com>, Alexandre Ghiti
<alexghiti@...osinc.com>, Steve Capper <steve.capper@...aro.org>, Kevin
Brodsky <kevin.brodsky@....com>, linux-arm-kernel@...ts.infradead.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 00/16] hugetlb and vmalloc fixes and perf
improvements
On Wed, 5 Feb 2025 15:09:40 +0000 Ryan Roberts <ryan.roberts@....com> wrote:
> I'm guessing that going in
> through the arm64 tree is the right approach here?
Seems that way, just from the line counts.
I suggest two series - one for the four cc:stable patches and one for
the 6.14 material. This depends on whether the ARM maintainers want to
get patches 1-4 into the -stable stream before the 6.14 release.
Powered by blists - more mailing lists