All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: akpm@linux-foundation.org, bp@suse.de, brgerst@gmail.com,
	dave.hansen@intel.com, dvlasenk@redhat.com, elliott@hpe.com,
	jpoimboe@redhat.com, luto@kernel.org, mingo@kernel.org,
	n-horiguchi@ah.jp.nec.com, peterz@infradead.org,
	tglx@linutronix.de, torvalds@linux-foundation.org,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] x86/mm, mm/hwpoison: Don't unconditionally unmap kernel 1:1" failed to apply to 4.15-stable tree
Date: Wed, 21 Feb 2018 10:31:17 +0100	[thread overview]
Message-ID: <20180221093117.GA16575@kroah.com> (raw)
In-Reply-To: <20180220185115.5jwk4nnev6voj724@agluck-desk>

On Tue, Feb 20, 2018 at 10:51:16AM -0800, Luck, Tony wrote:
> On Tue, Feb 20, 2018 at 04:34:00PM +0100, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 4.15-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>.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> > ------------------ original commit in Linus's tree ------------------
> > 
> > From fd0e786d9d09024f67bd71ec094b110237dc3840 Mon Sep 17 00:00:00 2001
> > From: Tony Luck <tony.luck@intel.com>
> > Date: Thu, 25 Jan 2018 14:23:48 -0800
> > Subject: [PATCH] x86/mm, mm/hwpoison: Don't unconditionally unmap kernel 1:1
> >  pages
> 
> Number of arguments to memory_failure() changed.
> 
> Updated patch (good for both v4.14-stable and v4.15-stable) below:

Thanks for the backport, now applied.

greg k-h

      reply	other threads:[~2018-02-21  9:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 15:34 FAILED: patch "[PATCH] x86/mm, mm/hwpoison: Don't unconditionally unmap kernel 1:1" failed to apply to 4.15-stable tree gregkh
2018-02-20 18:51 ` Luck, Tony
2018-02-21  9:31   ` Greg KH [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=20180221093117.GA16575@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@suse.de \
    --cc=brgerst@gmail.com \
    --cc=dave.hansen@intel.com \
    --cc=dvlasenk@redhat.com \
    --cc=elliott@hpe.com \
    --cc=jpoimboe@redhat.com \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.org \
    /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.