[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240717130030.09a778a38aae6a23a193b357@linux-foundation.org>
Date: Wed, 17 Jul 2024 13:00:30 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Hildenbrand <david@...hat.com>
Cc: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@...el.com>,
"peili.dev@...il.com" <peili.dev@...il.com>, "Nikula, Jani"
<jani.nikula@...el.com>, "Saarinen, Jani" <jani.saarinen@...el.com>,
"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@...el.com>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject: Re: Regression on linux-next (next-20240712)
On Wed, 17 Jul 2024 13:00:58 +0200 David Hildenbrand <david@...hat.com> wrote:
> > Could you please check why the patch causes this regression and provide a fix if necessary?
>
> This is know.
>
> There is a discussion along the original patch [1] on how to do it
> differently. But likely we'll tackle it differently [2]. So this patch
> should be dropped for -- which I think already happened because I cannot
> spot that patch in mm-unstable anymore.
Yes, I dropped it on July 15.
Powered by blists - more mailing lists