From: David Hildenbrand <david@redhat.com>
To: Sasha Levin <sashal@kernel.org>, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.com>, Minchan Kim <minchan@kernel.org>,
Huang Ying <ying.huang@intel.com>,
Wei Yang <richard.weiyang@gmail.com>,
Mel Gorman <mgorman@techsingularity.net>,
stable@vger.kernel.org
Subject: Re: [PATCH v3 1/3] mm/shuffle: don't move pages between zones and don't read garbage memmaps
Date: Mon, 6 Jul 2020 10:11:50 +0200 [thread overview]
Message-ID: <f263571b-8852-02c9-f606-9dc013b8124f@redhat.com> (raw)
In-Reply-To: <20200701193322.E670F20760@mail.kernel.org>
On 01.07.20 21:33, Sasha Levin wrote:
> Hi
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag
> fixing commit: e900a918b098 ("mm: shuffle initial free memory to improve memory-side-cache utilization").
>
> The bot has tested the following trees: v5.7.6, v5.4.49.
>
> v5.7.6: Build OK!
> v5.4.49: Failed to apply! Possible dependencies:
> e03d1f78341e8 ("mm/sparse: rename pfn_present() to pfn_in_present_section()")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
>
It contains
Cc: <stable@vger.kernel.org> [5.2+]
so a stable backport is desired once upstream. The v5.4.49 backport
should be fairly easy.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-07-06 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 9:47 [PATCH v3 0/3] mm/shuffle: fix and cleanups David Hildenbrand
2020-06-24 9:47 ` [PATCH v3 1/3] mm/shuffle: don't move pages between zones and don't read garbage memmaps David Hildenbrand
2020-07-01 19:33 ` Sasha Levin
2020-07-02 7:24 ` David Hildenbrand
2020-07-06 8:11 ` David Hildenbrand [this message]
2020-07-10 14:03 ` Sasha Levin
2020-06-24 9:47 ` [PATCH v3 2/3] mm/memory_hotplug: document why shuffle_zone() is relevant David Hildenbrand
2020-06-24 9:47 ` [PATCH v3 3/3] mm/shuffle: remove dynamic reconfiguration 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=f263571b-8852-02c9-f606-9dc013b8124f@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=richard.weiyang@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).