From: James Morse <james.morse@arm.com>
To: Greg KH <gregkh@linuxfoundation.org>, rafael.j.wysocki@intel.com
Cc: 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.4-stable tree
Date: Mon, 27 Nov 2017 10:09:31 +0000 [thread overview]
Message-ID: <5A1BE45B.4050706@arm.com> (raw)
In-Reply-To: <20171125180628.GB6302@kroah.com>
Hi Greg,
On 25/11/17 18:06, Greg KH wrote:
> On Sat, Nov 25, 2017 at 02:54:08PM +0100, 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.4-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.4 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.
>>
>
> Dropped from all stable queues now. Why was this even a stable patch at
> all anyway? It doesn't fix anything...
It looks like this series picked up a 'Cc: All applicable
<stable@vger.kernel.org>' along the way. (Rafael?)
The first patch fixed the problem, the rest were clean-up, code we no longer
needed and hooks that had no more users in v4.14.
I can provide backports back to v4.13, which is when arm64 got APEI support, but
before then I have nothing to test it on...
Can I suggest dropping this series from the stable trees? (do you need me to
reply to each email?)
Thanks,
James
next prev parent reply other threads:[~2017-11-27 10:11 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.4-stable tree gregkh
2017-11-25 18:06 ` Greg KH
2017-11-27 10:09 ` James Morse [this message]
2017-11-27 11:41 ` Greg KH
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=5A1BE45B.4050706@arm.com \
--to=james.morse@arm.com \
--cc=bp@suse.de \
--cc=gregkh@linuxfoundation.org \
--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.