From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Linux 4.4.112-cip18
Date: Fri, 26 Jan 2018 17:42:32 +0000 [thread overview]
Message-ID: <1516988552.3417.54.camel@codethink.co.uk> (raw)
I've released Linux version 4.4.112-cip18.??A summary of the changes
since 4.4.105-cip15:
- Merge fixes from stable versions 4.4.106-4.4.112 inclusive
- Includes mitigation for Meltdown on x86_64 only
- Apply related fixes to hpsa driver and deadline scheduler
- Fix regressions in nfsd, x86 microcode loader, and x86_64 vsyscall
- Fix r8a7743 watchdog timer clock definition
I also tagged intermediate versions 4.4.109-cip16 and 4.4.112-cip17.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
reply other threads:[~2018-01-26 17:42 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=1516988552.3417.54.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox