From: Greg KH <gregkh@linuxfoundation.org>
To: Will Deacon <will.deacon@arm.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
ard.biesheuvel@linaro.org
Subject: Re: [GIT PULL] arm64 spectre and meltdown mitigations for -stable
Date: Wed, 21 Feb 2018 13:53:40 +0100 [thread overview]
Message-ID: <20180221125340.GA15211@kroah.com> (raw)
In-Reply-To: <20180209134811.GB11309@arm.com>
On Fri, Feb 09, 2018 at 01:48:11PM +0000, Will Deacon wrote:
> Hi Greg,
>
> I've put together a tag which includes all of the upstream arm64 spectre and
> meltdown mitigations based on v4.15. Please could you consider taking this
> into the 4.15 stable tree?
>
> I understand that Ard (cc'd) is using this stack to create a version for 4.14
> too.
Do you know of anyone working on backporting this patch series to older
stable trees (i.e. 4.9.y and 4.4.y and possibly 3.18.y?)
I had some requests by some chip manufacturers who were wondering about
this, as they seem to be stuck on older kernels (of their own doing, not
our fault at all...)
If not, no big deal, I'll just tell them they need to do the work
themselves if they care about those old kernel trees :)
thanks,
greg k-h
next prev parent reply other threads:[~2018-02-21 13:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 13:48 [GIT PULL] arm64 spectre and meltdown mitigations for -stable Will Deacon
2018-02-09 13:49 ` Greg KH
2018-02-09 13:51 ` Will Deacon
2018-02-09 15:04 ` Greg KH
2018-02-13 16:48 ` Greg KH
2018-02-14 12:41 ` Will Deacon
2018-02-14 12:54 ` Greg KH
2018-02-14 13:56 ` Greg KH
2018-02-21 12:53 ` Greg KH [this message]
2018-02-21 13:43 ` Ard Biesheuvel
2018-02-21 13:47 ` 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=20180221125340.GA15211@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).