From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
Mikhail Zaslonko <zaslonko@linux.ibm.com>,
akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
stable@vger.kernel.orgstable@vger.kernel.org
Subject: Re: [PATCH 1/1] mm, memory_hotplug: Initialize struct pages for the full memory section
Date: Mon, 10 Dec 2018 21:09:22 +0000 [thread overview]
Message-ID: <20181210210922.D68472084E@mail.kernel.org> (raw)
In-Reply-To: <20181210130712.30148-2-zaslonko@linux.ibm.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v4.19.8, v4.14.87, v4.9.144, v4.4.166, v3.18.128,
v4.19.8: Failed to apply! Possible dependencies:
Unable to calculate
v4.14.87: Failed to apply! Possible dependencies:
Unable to calculate
v4.9.144: Failed to apply! Possible dependencies:
Unable to calculate
v4.4.166: Failed to apply! Possible dependencies:
Unable to calculate
v3.18.128: Failed to apply! Possible dependencies:
Unable to calculate
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-12-10 21:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 13:07 [PATCH 0/1] Initialize struct pages for the full section Mikhail Zaslonko
2018-12-10 13:07 ` [PATCH 1/1] mm, memory_hotplug: Initialize struct pages for the full memory section Mikhail Zaslonko
2018-12-10 13:24 ` Michal Hocko
2018-12-10 15:45 ` Zaslonko Mikhail
2018-12-10 18:19 ` Michal Hocko
2018-12-11 15:18 ` Zaslonko Mikhail
2018-12-11 9:49 ` Wei Yang
2018-12-11 15:17 ` Zaslonko Mikhail
2018-12-11 22:24 ` Wei Yang
2018-12-10 15:10 ` Wei Yang
2018-12-10 16:14 ` Zaslonko Mikhail
2018-12-11 1:50 ` Wei Yang
2018-12-11 15:23 ` Zaslonko Mikhail
2018-12-11 22:14 ` Wei Yang
2018-12-10 21:09 ` Sasha Levin [this message]
2019-06-14 21:56 ` Sasha Levin
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=20181210210922.D68472084E@mail.kernel.org \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.orgstable \
--cc=zaslonko@linux.ibm.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).