From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: L!TF Bulletin #2: State of the horrors
Date: Mon, 2 Jul 2018 23:49:55 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1807022332240.1590@nanos.tec.linutronix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
Hi!
I've updated the repository (master branch and the 4.17/16/14.y stable
branches) with the following items since the last bulletin, i.e. on top of
7ce2f0393ea2 ("x86/CPU/AMD: Move TOPOEXT reenablement before reading
smp_num_siblings"):
- PAE swap protection (Vlastimil)
- PTE->PFN conversion kleenup for PAE (Michal)
- The nosmt=force handling of the Massive Cake Engineering trainwreck.
The KVM bits are not yet in the repository, but they seem to converge now.
Find the latest L!TF combo bundle based on 4.18-rc1 attached.
Thanks,
tglx
[-- Attachment #2: Type: application/octet-stream, Size: 42767 bytes --]
reply other threads:[~2018-07-02 21:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1807022332240.1590@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).