[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231003090443.67a2e2692b68211e05b53248@linux-foundation.org>
Date: Tue, 3 Oct 2023 09:04:43 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Alexandre Ghiti <alex@...ti.fr>
Cc: Alexandre Ghiti <alexghiti@...osinc.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Andrew Jones <ajones@...tanamicro.com>,
Qinglin Pan <panqinglin2020@...as.ac.cn>,
Ryan Roberts <ryan.roberts@....com>,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH -fixes 0/2] Fix set_huge_pte_at()
On Tue, 3 Oct 2023 17:43:10 +0200 Alexandre Ghiti <alex@...ti.fr> wrote:
> +cc Andrew: Would you mind taking this patchset in your tree for the
> next rc? This patchset depends on a previous fix for arm64 that you
> merged in rc4 which is not in the riscv -fixes branch yet.
>
> I saw with Palmer and he should ack this shortly.
Well I grabbed them into mm.git's mm-hotfixes-unstable queue. All
being well I'll move them into mm-hotfixes-stable within a week then
into Linus shortly after.
Unless something changes. It's odd that the riscv tree(s) aren't set
up to merge fixes against -rc4?
Powered by blists - more mailing lists