From: Greg KH <greg@kroah.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 0/9] s390 spectre update for 4.14
Date: Wed, 23 May 2018 19:40:50 +0200 [thread overview]
Message-ID: <20180523174050.GA2622@kroah.com> (raw)
In-Reply-To: <1527092529-24383-1-git-send-email-schwidefsky@de.ibm.com>
On Wed, May 23, 2018 at 06:22:00PM +0200, Martin Schwidefsky wrote:
> Hi Greg,
>
> 9 more patches against the 2018/05/23 linux-4.14.y stable branch.
> This gets the spectre defense of 4.14 up-to-date compared to the
> current upstream tree. The upstream patches to remove the indirect
> branches from the BPF JIT are included (these do not have a
> CC:stable tag).
All now applied, thanks.
greg k-h
prev parent reply other threads:[~2018-05-23 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 16:22 [PATCH 0/9] s390 spectre update for 4.14 Martin Schwidefsky
2018-05-23 16:22 ` [PATCH 1/9] s390: add assembler macros for CPU alternatives Martin Schwidefsky
2018-05-23 16:22 ` [PATCH 2/9] s390: move expoline assembler macros to a header Martin Schwidefsky
2018-05-23 16:22 ` [PATCH 3/9] s390/crc32-vx: use expoline for indirect branches Martin Schwidefsky
2018-05-23 16:22 ` [PATCH 4/9] s390/lib: " Martin Schwidefsky
2018-05-23 16:22 ` [PATCH 5/9] s390/ftrace: " Martin Schwidefsky
2018-05-23 16:22 ` [PATCH 6/9] s390/kernel: " Martin Schwidefsky
2018-05-23 16:22 ` [PATCH 7/9] s390: move spectre sysfs attribute code Martin Schwidefsky
2018-05-23 16:22 ` [PATCH 8/9] s390: extend expoline to BC instructions Martin Schwidefsky
2018-05-23 16:22 ` [PATCH 9/9] s390: use expoline thunks in the BPF JIT Martin Schwidefsky
2018-05-23 17:40 ` 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=20180523174050.GA2622@kroah.com \
--to=greg@kroah.com \
--cc=schwidefsky@de.ibm.com \
--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.