From: Andrew Morton <akpm@linux-foundation.org>
To: Laurent Dufour <ldufour@linux.ibm.com>
Cc: David Hildenbrand <david@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Oscar Salvador <osalvador@suse.de>,
mhocko@suse.com, linux-mm@kvack.org,
"Rafael J . Wysocki" <rafael@kernel.org>,
nathanl@linux.ibm.com, cheloha@linux.ibm.com,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v3 1/3] mm: replace memmap_context by meminit_context
Date: Wed, 16 Sep 2020 16:37:56 -0700 [thread overview]
Message-ID: <20200916163756.af1bece4bbd1937a20a727df@linux-foundation.org> (raw)
In-Reply-To: <f522bcb8-575e-0ac7-69cb-1064e8b38c58@linux.ibm.com>
On Wed, 16 Sep 2020 18:09:55 +0200 Laurent Dufour <ldufour@linux.ibm.com> wrote:
> >>> It's up to the maintainer what they want, but as it is, this patch is
> >>> not going to end up in stable kernel release (which it looks like is the
> >>> right thing to do...)
> >>
> >> Thanks a lot Greg.
> >>
> >> I'll send that single patch again with the Cc: stable tag.
> >
> > I think Andrew can add that when sending upstream.
>
> Andrew, can you do that?
>
I did.
Patches 1 & 2 are cc:stable, patch 3 is not.
I'll queue up 1 & 2 for a 5.9-rcX merge.
next prev parent reply other threads:[~2020-09-16 23:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 9:41 [PATCH v3 0/3] mm: fix memory to node bad links in sysfs Laurent Dufour
2020-09-15 9:41 ` [PATCH v3 1/3] mm: replace memmap_context by memplug_context Laurent Dufour
2020-09-15 10:17 ` David Hildenbrand
2020-09-15 10:28 ` Oscar Salvador
2020-09-15 12:15 ` Michal Hocko
2020-09-15 13:26 ` [PATCH v3 1/3] mm: replace memmap_context by meminit_context Laurent Dufour
2020-09-15 13:35 ` Michal Hocko
2020-09-16 6:33 ` Greg Kroah-Hartman
2020-09-16 7:29 ` Laurent Dufour
2020-09-16 7:40 ` Greg Kroah-Hartman
2020-09-16 7:47 ` Laurent Dufour
2020-09-16 7:52 ` David Hildenbrand
2020-09-16 16:09 ` Laurent Dufour
2020-09-16 23:37 ` Andrew Morton [this message]
2020-09-17 8:00 ` Laurent Dufour
2020-09-15 9:41 ` [PATCH v3 2/3] mm: don't rely on system state to detect hot-plug operations Laurent Dufour
2020-09-15 10:31 ` Oscar Salvador
2020-09-15 12:19 ` Michal Hocko
2020-09-15 9:41 ` [PATCH v3 3/3] mm: don't panic when links can't be created in sysfs Laurent Dufour
2020-09-15 10:33 ` Oscar Salvador
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=20200916163756.af1bece4bbd1937a20a727df@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cheloha@linux.ibm.com \
--cc=david@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ldufour@linux.ibm.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=nathanl@linux.ibm.com \
--cc=osalvador@suse.de \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tony.luck@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