From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Laurent Dufour <ldufour@linux.ibm.com>
Cc: stable@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Michal Hocko <mhocko@suse.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Fenghua Yu <fenghua.yu@intel.com>,
Nathan Lynch <nathanl@linux.ibm.com>,
Scott Cheloha <cheloha@linux.ibm.com>,
Tony Luck <tony.luck@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 2/2] mm: don't rely on system state to detect hot-plug operations
Date: Mon, 5 Oct 2020 15:06:19 +0200 [thread overview]
Message-ID: <20201005130619.GC827657@kroah.com> (raw)
In-Reply-To: <20200929162250.67282-2-ldufour@linux.ibm.com>
On Tue, Sep 29, 2020 at 06:22:50PM +0200, Laurent Dufour wrote:
> Backport version to the 4.19-stable tree of:
> [ Upstream commit f85086f95fa36194eb0db5cd5c12e56801b98523 ]
Both series, now queued up, thanks!
gre gk-h
next prev parent reply other threads:[~2020-10-05 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 16:22 [PATCH 1/2] mm: replace memmap_context by memplug_context Laurent Dufour
2020-09-29 16:22 ` [PATCH 2/2] mm: don't rely on system state to detect hot-plug operations Laurent Dufour
2020-10-05 13:06 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-29 16:12 [PATCH 1/2] mm: replace memmap_context by memplug_context Laurent Dufour
2020-09-29 16:12 ` [PATCH 2/2] mm: don't rely on system state to detect hot-plug operations Laurent Dufour
2020-09-29 14:03 [PATCH 1/2] mm: replace memmap_context by memplug_context Laurent Dufour
2020-09-29 14:03 ` [PATCH 2/2] mm: don't rely on system state to detect hot-plug operations Laurent Dufour
2020-09-29 13:57 [PATCH 1/2] mm: replace memmap_context by memplug_context Laurent Dufour
2020-09-29 13:57 ` [PATCH 2/2] mm: don't rely on system state to detect hot-plug operations Laurent Dufour
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=20201005130619.GC827657@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=cheloha@linux.ibm.com \
--cc=david@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=ldufour@linux.ibm.com \
--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 \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.