From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Nadav Amit <namit@vmware.com>
Cc: Andi Kleen <ak@linux.intel.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"jpoimboe@redhat.com" <jpoimboe@redhat.com>,
"luto@kernel.org" <luto@kernel.org>,
"mhocko@suse.com" <mhocko@suse.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"sean.j.christopherson@intel.com"
<sean.j.christopherson@intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] x86/mm: Use WRITE_ONCE() when setting PTEs" failed to apply to 4.18-stable tree
Date: Mon, 17 Sep 2018 20:16:44 +0200 [thread overview]
Message-ID: <20180917181644.GA3201@kroah.com> (raw)
In-Reply-To: <E7CC7A59-DFFE-4ED7-81FD-D91EC42D3725@vmware.com>
On Mon, Sep 17, 2018 at 04:56:11PM +0000, Nadav Amit wrote:
> at 9:42 AM, Andi Kleen <ak@linux.intel.com> wrote:
>
> > On Sun, Sep 16, 2018 at 02:42:16PM +0200, gregkh@linuxfoundation.org wrote:
> >> The patch below does not apply to the 4.18-stable tree.
> >> If someone wants it applied there, or to any other stable or longterm
> >> tree, then please email the backport, including the original git commit
> >> id to <stable@vger.kernel.org>.
> >
> > I don't think the patch is really needed for stable because
> > it's mainly a theoretical issue
> >
> > (unless it's needed as a dependency for some later patch)
>
> Perfectly fine with me. Greg, let me know if you still want me to send a
> patch for old stable trees.
>
If it's not good enough for 4.18.y, then no need for any older kernel,
thanks.
greg k-h
prev parent reply other threads:[~2018-09-17 23:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 12:42 FAILED: patch "[PATCH] x86/mm: Use WRITE_ONCE() when setting PTEs" failed to apply to 4.18-stable tree gregkh
2018-09-17 16:42 ` Andi Kleen
2018-09-17 16:56 ` Nadav Amit
2018-09-17 18:16 ` gregkh [this message]
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=20180917181644.GA3201@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ak@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=jpoimboe@redhat.com \
--cc=luto@kernel.org \
--cc=mhocko@suse.com \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=sean.j.christopherson@intel.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
/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).