All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: speck@linutronix.de
Subject: [MODERATED] Re: L!TF Bulletin #8: The final bits
Date: Wed, 8 Aug 2018 16:43:03 +0200	[thread overview]
Message-ID: <20180808144303.GA20974@kroah.com> (raw)
In-Reply-To: <1533724479.3615.42.camel@infradead.org>

On Wed, Aug 08, 2018 at 11:34:40AM +0100, speck for David Woodhouse wrote:
> 
> 
> On Wed, 2018-08-08 at 09:37 +0200, speck for Thomas Gleixner wrote:
> > Hi!
> > 
> > I've merged the SMT fix and parts of Andis PTE inversion series:
> > 
> > 958f79b9ee55 ("x86/mm/pat: Make set_memory_np() L1TF safe")
> > 0768f91530ff ("x86/speculation/l1tf: Make pmd/pud_mknotpresent() invert")
> > f22cc87f6c1f ("x86/speculation/l1tf: Invert all not present mappings")
> > bc2d8d262cba ("cpu/hotplug: Fix SMT supported evaluation")
> > 
> > The branches are updated and pushed out. The resulting bundles are
> > attached.
> > 
> > I'm leaving for the summer camp now, but I'll have a look once per day into
> > the list and if no reports come in until the weekend I'll prepare the pull
> > request for Linus from what we have now.
> > 
> > Please give it a proper testing.
> 
> I've updated the 4.9 branch. I also have this to add on top, with
> slight tweaks for each of the stable branches. Want me to just push
> those?

I have some initial patches that Guenter made up for 4.4 that ignores
the KVM stuff, as odds are those will be good to get merged.  Should I
post them here or push them to the git tree?  I haven't checked to see
if I have write permissions...

Or should I just not worry about it and queue them up in my stable trees
when the embargo lifts?


thanks,

greg k-h

  reply	other threads:[~2018-08-08 14:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08  7:37 L!TF Bulletin #8: The final bits Thomas Gleixner
2018-08-08 10:34 ` [MODERATED] " David Woodhouse
2018-08-08 14:43   ` Greg KH [this message]
2018-08-08 19:33     ` Thomas Gleixner
2018-08-10 10:05       ` [MODERATED] " Greg KH
2018-08-08 19:35   ` 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=20180808144303.GA20974@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --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.