From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: Re: Updated L1TF native OS patch
Date: Wed, 2 May 2018 14:04:38 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1805021403410.1560@nanos.tec.linutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1805021247570.1668@nanos.tec.linutronix.de>
On Wed, 2 May 2018, speck for Thomas Gleixner wrote:
> On Tue, 1 May 2018, speck for Andi Kleen wrote:
> > On Tue, May 01, 2018 at 05:05:12PM -0700, speck for Andi Kleen wrote:
> > > On Tue, May 01, 2018 at 04:59:53PM -0700, speck for Linus Torvalds wrote:
> > > >
> > > >
> > > > On Tue, 1 May 2018, speck for Andi Kleen wrote:
> > > > >
> > > > > Here's a v2 of the L1TF native OS patch kit.
> > > >
> > > > Hmm. I got 1/6 three times, but not any of the others..
> > >
> > > Sorry I had some troubles with the gpg scripting. I sent
> > > them manually now. Hopefully this works.
>
> What's the problem? Does that speckify-mbox script not work for you?
>
> > Also attaching the unencrypted mbox for easier applying etc.
>
> Remailing it right now.
How on earth did you generate that mbox? There's no message ID, random
dates and whatever.
next prev parent reply other threads:[~2018-05-02 12:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 23:42 [MODERATED] Updated L1TF native OS patch Andi Kleen
2018-05-01 23:59 ` [MODERATED] " Linus Torvalds
2018-05-02 0:05 ` Andi Kleen
2018-05-02 1:21 ` Andi Kleen
2018-05-02 8:04 ` Peter Zijlstra
2018-05-02 10:48 ` Thomas Gleixner
2018-05-02 12:04 ` Thomas Gleixner [this message]
2018-05-02 14:50 ` [MODERATED] " Andi Kleen
2018-05-02 14:53 ` Thomas Gleixner
2018-05-02 12:14 ` [MODERATED] " Michal Hocko
2018-05-02 12:36 ` Thomas Gleixner
2018-05-02 12:44 ` [MODERATED] " Michal Hocko
2018-05-02 15:07 ` Andi Kleen
2018-05-02 15:35 ` Michal Hocko
2018-05-02 16:08 ` Andi Kleen
2018-05-03 9:26 ` Michal Hocko
2018-05-03 10:04 ` Michal Hocko
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=alpine.DEB.2.21.1805021403410.1560@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--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.