From: Andrew Morton <akpm@linux-foundation.org>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Aneesh Kumar K V <aneesh.kumar@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org, Wei Xu <weixugc@google.com>,
Yang Shi <shy828301@gmail.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Tim C Chen <tim.c.chen@intel.com>,
Michal Hocko <mhocko@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hesham Almatary <hesham.almatary@huawei.com>,
Dave Hansen <dave.hansen@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Alistair Popple <apopple@nvidia.com>,
Dan Williams <dan.j.williams@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
jvgediya.oss@gmail.com, Bharata B Rao <bharata@amd.com>
Subject: Re: [PATCH] mm/demotion: Fix kernel error with memory hotplug
Date: Thu, 25 Aug 2022 20:04:28 -0700 [thread overview]
Message-ID: <20220825200428.5d42ff3ecac4a0dc3a5d0020@linux-foundation.org> (raw)
In-Reply-To: <87k06v3l6h.fsf@yhuang6-desk2.ccr.corp.intel.com>
On Fri, 26 Aug 2022 08:25:42 +0800 "Huang, Ying" <ying.huang@intel.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.
next prev parent reply other threads:[~2022-08-26 3:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 9:20 Aneesh Kumar K.V
2022-08-25 12:16 ` David Hildenbrand
2022-08-25 12:53 ` Aneesh Kumar K V
2022-08-26 0:25 ` Huang, Ying
2022-08-26 3:04 ` Andrew Morton [this message]
2022-08-26 9:53 ` David Hildenbrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220825200428.5d42ff3ecac4a0dc3a5d0020@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=apopple@nvidia.com \
--cc=bharata@amd.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hesham.almatary@huawei.com \
--cc=jvgediya.oss@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shy828301@gmail.com \
--cc=tim.c.chen@intel.com \
--cc=weixugc@google.com \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox