From: Jon Masters <jcm@jonmasters.org>
To: Timur Tabi <timur@codeaurora.org>, lkml <linux-kernel@vger.kernel.org>
Cc: Shanker Donthineni <shankerd@codeaurora.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Will Deacon <will.deacon@arm.com>,
stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "[Variant 2/Spectre-v2] arm64: Implement branch predictor hardening for Falkor" has been added to the 4.14-stable tree
Date: Mon, 19 Feb 2018 18:57:12 -0500 [thread overview]
Message-ID: <5be20f44-b750-7250-76a8-03b6c39bb2fe@jonmasters.org> (raw)
In-Reply-To: <CAOZdJXWZV4TDZchsYeHE_Oh+s1y3yjXE9NxVY9wz-vCkZVhN4w@mail.gmail.com>
On 02/14/2018 11:16 AM, Timur Tabi wrote:
> On Wed, Feb 14, 2018 at 7:53 AM, <gregkh@linuxfoundation.org> wrote:
>>
>> This is a note to let you know that I've just added the patch titled
>>
>> [Variant 2/Spectre-v2] arm64: Implement branch predictor hardening for Falkor
>>
>> to the 4.14-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:
>> arm64-implement-branch-predictor-hardening-for-falkor.patch
>> and it can be found in the queue-4.14 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.
>
> Please note that there is a follow-on patch, also from Shanker, that
> fixes this patch (it was slightly mangled when merged into 4.16-rc1):
>
> https://www.spinics.net/lists/arm-kernel/msg633726.html
>
> I would love for it to be included in 4.14.20, but it hasn't been
> merged into Linus' tree yet. I will send a patch request when it does
> land in 4.16-rc2.
That has now landed in Linus's tree.
Jon.
next prev parent reply other threads:[~2018-02-19 23:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1518616386206238@kroah.com>
2018-02-14 16:16 ` Timur Tabi
2018-02-14 18:23 ` Greg Kroah-Hartman
2018-02-14 18:49 ` Catalin Marinas
2018-02-19 23:57 ` Jon Masters [this message]
2018-02-20 10:47 ` Greg Kroah-Hartman
2018-02-20 10:49 ` Greg Kroah-Hartman
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=5be20f44-b750-7250-76a8-03b6c39bb2fe@jonmasters.org \
--to=jcm@jonmasters.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shankerd@codeaurora.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=timur@codeaurora.org \
--cc=will.deacon@arm.com \
/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
all inboxes | Powered by JetHome®