From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 5/8] L1TFv7 0
Date: Tue, 12 Jun 2018 16:58:44 -0400 [thread overview]
Message-ID: <20180612205844.GL25607@char.us.oracle.com> (raw)
In-Reply-To: <20180607232832.GI7220@tassilo.jf.intel.com>
On Thu, Jun 07, 2018 at 04:28:32PM -0700, speck for Andi Kleen wrote:
> On Thu, Jun 07, 2018 at 04:22:25PM -0700, speck for ak_at_linux.intel.com wrote:
> > From: Andi Kleen <ak@linux.intel.com>
> > Subject: x86/speculation/l1tf: Add sysfs reporting for l1tf
> >
> > L1TF core kernel workarounds are cheap and normally always enabled,
> > However we still want to report in sysfs if the system is vulnerable
> > or mitigated. Add the necessary checks.
>
> mbox for easier applying attached.
Oddly enough I had to modify it and do
s/>From/From/
Not sure where the '>' came from.
Thanks!
next prev parent reply other threads:[~2018-06-12 20:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 23:22 [MODERATED] [PATCH 0/8] L1TFv7 3 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 1/8] L1TFv7 1 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 2/8] L1TFv7 4 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 3/8] L1TFv7 8 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 4/8] L1TFv7 6 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 5/8] L1TFv7 0 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 6/8] L1TFv7 7 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 7/8] L1TFv7 2 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 8/8] L1TFv7 5 ak
[not found] ` <20180607232533.A6E2361102@crypto-ml.lab.linutronix.de>
2018-06-07 23:28 ` [MODERATED] Re: [PATCH 5/8] L1TFv7 0 Andi Kleen
2018-06-12 20:58 ` Konrad Rzeszutek Wilk [this message]
[not found] ` <20180607232458.6463361106@crypto-ml.lab.linutronix.de>
2018-06-07 23:34 ` [MODERATED] Re: [PATCH 1/8] L1TFv7 1 Dave Hansen
[not found] ` <20180607232537.C80D26114D@crypto-ml.lab.linutronix.de>
2018-06-12 15:02 ` [PATCH 5/8] L1TFv7 0 Thomas Gleixner
[not found] ` <20180607232608.B2E4661189@crypto-ml.lab.linutronix.de>
2018-06-12 15:03 ` [PATCH 6/8] L1TFv7 7 Thomas Gleixner
[not found] ` <20180607232452.BB0E3610FC@crypto-ml.lab.linutronix.de>
2018-06-12 16:13 ` [PATCH 2/8] L1TFv7 4 Thomas Gleixner
[not found] ` <20180607232536.1127561149@crypto-ml.lab.linutronix.de>
2018-06-12 17:35 ` [MODERATED] Re: [PATCH 5/8] L1TFv7 0 Jon Masters
2018-06-12 18:41 ` Thomas Gleixner
2018-06-12 18:47 ` [MODERATED] " Jon Masters
2018-06-12 19:03 ` Thomas Gleixner
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=20180612205844.GL25607@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=speck@linutronix.de \
/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.