From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: David Rientjes <rientjes@google.com>,
mm-commits@vger.kernel.org, xemul@virtuozzo.com, vbabka@suse.cz,
Michal Hocko <mhocko@kernel.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Mike Rapoport <rppt@linux.ibm.com>,
Andrei Vagin <avagin@gmail.com>,
stable@vger.kernel.org
Subject: Re: [nacked] mm-thp-always-specify-disabled-vmas-as-nh-in-smaps.patch removed from -mm tree
Date: Wed, 30 Jan 2019 18:07:30 +0300 [thread overview]
Message-ID: <20190130150730.GI2332@uranus.lan> (raw)
In-Reply-To: <20190130144649.A532E218A3@mail.kernel.org>
On Wed, Jan 30, 2019 at 02:46:48PM +0000, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 1860033237d4 mm: make PR_SET_THP_DISABLE immediately active.
>
> The bot has tested the following trees: v4.20.5, v4.19.18, v4.14.96.
>
> v4.20.5: Build OK!
> v4.19.18: Build OK!
> v4.14.96: Failed to apply! Possible dependencies:
> f66406638fff ("proc: replace seq_printf on seq_putc to speed up /proc/pid/smaps")
>
>
> How should we proceed with this patch?
We shouldn't. It is a false positive due to Fixes flag.
next prev parent reply other threads:[~2019-01-30 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 22:09 [nacked] mm-thp-always-specify-disabled-vmas-as-nh-in-smaps.patch removed from -mm tree akpm
[not found] ` <20190130144649.A532E218A3@mail.kernel.org>
2019-01-30 15:07 ` Cyrill Gorcunov [this message]
2019-01-30 16:17 ` 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=20190130150730.GI2332@uranus.lan \
--to=gorcunov@gmail.com \
--cc=adobriyan@gmail.com \
--cc=avagin@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=mhocko@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rientjes@google.com \
--cc=rppt@linux.ibm.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
--cc=xemul@virtuozzo.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).