From: Greg KH <gregkh@linuxfoundation.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: keno@juliacomputing.com, akpm@linux-foundation.org,
ben@decadent.org.uk, gthelen@google.com, hughd@google.com,
keescook@chromium.org, kirill.shutemov@linux.intel.com,
luto@kernel.org, npiggin@gmail.com, oleg@redhat.com,
torvalds@linux-foundation.org, w@1wt.eu, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "mm/huge_memory.c: respect FOLL_FORCE/FOLL_COW for thp" has been added to the 4.4-stable tree
Date: Mon, 10 Apr 2017 18:05:16 +0200 [thread overview]
Message-ID: <20170410160516.GB5425@kroah.com> (raw)
In-Reply-To: <20170410153417.GH4618@dhcp22.suse.cz>
On Mon, Apr 10, 2017 at 05:34:17PM +0200, Michal Hocko wrote:
> On Mon 10-04-17 17:09:17, Greg KH wrote:
> [...]
> > >From 303681d5d538d81b5e23754515202b5b9febd2e9 Mon Sep 17 00:00:00 2001
> > From: Keno Fischer <keno@juliacomputing.com>
> > Date: Tue, 24 Jan 2017 15:17:48 -0800
> > Subject: mm/huge_memory.c: respect FOLL_FORCE/FOLL_COW for thp
> >
> > From: Keno Fischer <keno@juliacomputing.com>
> >
> > commit 8310d48b125d19fcd9521d83b8293e63eb1646aa upstream.
>
> This backport is wrong. See
> http://lkml.kernel.org/r/20170328131154.GH18241@dhcp22.suse.cz
No such Message-ID known.
:(
next prev parent reply other threads:[~2017-04-10 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 15:09 Patch "mm/huge_memory.c: respect FOLL_FORCE/FOLL_COW for thp" has been added to the 4.4-stable tree gregkh
2017-04-10 15:34 ` Michal Hocko
2017-04-10 16:05 ` Greg KH [this message]
2017-04-10 16:13 ` Michal Hocko
2017-04-10 15:48 ` Ben Hutchings
2017-04-10 16:04 ` Greg KH
2017-04-10 16:13 ` Michal Hocko
2017-04-10 16:21 ` Greg KH
2017-04-10 18:10 ` Ben Hutchings
2017-05-23 14:46 gregkh
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=20170410160516.GB5425@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=gthelen@google.com \
--cc=hughd@google.com \
--cc=keescook@chromium.org \
--cc=keno@juliacomputing.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=luto@kernel.org \
--cc=mhocko@kernel.org \
--cc=npiggin@gmail.com \
--cc=oleg@redhat.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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.