From: Greg KH <gregkh@linuxfoundation.org>
To: James Morse <james.morse@arm.com>
Cc: rafael.j.wysocki@intel.com, bp@suse.de, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "ACPI / APEI: Remove arch_apei_flush_tlb_one()" has been added to the 4.9-stable tree
Date: Mon, 27 Nov 2017 13:02:27 +0100 [thread overview]
Message-ID: <20171127120227.GA24404@kroah.com> (raw)
In-Reply-To: <5A1BFC4D.6040303@arm.com>
On Mon, Nov 27, 2017 at 11:51:41AM +0000, James Morse wrote:
> Hi Greg,
>
> On 25/11/17 13:54, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > ACPI / APEI: Remove arch_apei_flush_tlb_one()
> >
> > to the 4.9-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > acpi-apei-remove-arch_apei_flush_tlb_one.patch
> > and it can be found in the queue-4.9 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> I don't think this patch should applied to the stable trees:
>
> This patch is cleanup following 'ACPI / APEI: Replace ioremap_page_range() with
> fixmap', which failed to apply to this tree. Having this patch will lead to
> build-breakage with exotic Kconfig options!
"exotic" is just any normal x86 build :)
This was dropped from all of the stable trees already because the
previous patch did not apply.
thanks,
greg k-h
next prev parent reply other threads:[~2017-11-27 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 13:54 Patch "ACPI / APEI: Remove arch_apei_flush_tlb_one()" has been added to the 4.9-stable tree gregkh
2017-11-27 11:51 ` James Morse
2017-11-27 12:02 ` Greg KH [this message]
2017-11-27 12:10 ` James Morse
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=20171127120227.GA24404@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bp@suse.de \
--cc=james.morse@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.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.