[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220825200428.5d42ff3ecac4a0dc3a5d0020@linux-foundation.org>
Date: Thu, 25 Aug 2022 20:04:28 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Huang, Ying" <ying.huang@...el.com>
Cc: Aneesh Kumar K V <aneesh.kumar@...ux.ibm.com>,
David Hildenbrand <david@...hat.com>, linux-mm@...ck.org,
Wei Xu <weixugc@...gle.com>, Yang Shi <shy828301@...il.com>,
Davidlohr Bueso <dave@...olabs.net>,
Tim C Chen <tim.c.chen@...el.com>,
Michal Hocko <mhocko@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Hesham Almatary <hesham.almatary@...wei.com>,
Dave Hansen <dave.hansen@...el.com>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Alistair Popple <apopple@...dia.com>,
Dan Williams <dan.j.williams@...el.com>,
Johannes Weiner <hannes@...xchg.org>, jvgediya.oss@...il.com,
Bharata B Rao <bharata@....com>
Subject: Re: [PATCH] mm/demotion: Fix kernel error with memory hotplug
On Fri, 26 Aug 2022 08:25:42 +0800 "Huang, Ying" <ying.huang@...el.com> wrote:
> >> Do we have to cc stable?
> >>
> >
> > That patch is not yet merged upstream. It is in mm-unstable. I guess Andrew can fold the change
> > into the original patch?
>
> I think it may better to reply the original patch and name this patch as
> fix, for example,
>
> mm/demotion: Add hotplug callbacks to handle new numa node onlined fix
>
> I found Andrew uses this kind of name before for fixing.
Doesn't matter much - figuring out which-patch-did-this-patch-fix is,
shall we say, a common operation at akpm headquarters ;)
This was an easy one, thanks to the Fixes:. The patch didn't actually
apply at the desired point in the series, and that's pretty common.
All fixed up now, thanks.
Powered by blists - more mailing lists