From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Linux 4.4.154-cip28
Date: Wed, 12 Sep 2018 21:25:32 +0100 [thread overview]
Message-ID: <1536783932.3024.208.camel@codethink.co.uk> (raw)
I've released Linux version 4.4.154-cip28.??A summary of the changes
since 4.4.138-cip25:
- Add alignment quirk for USB network gadget drivers on Renesas USBHS,
so they can use DMA
- Fix log level for an error message in PM/OPP core
- Add support for critical clocks
- Add support for the Renesas R8A7745 (RZ/G1E) and iW-RainboW-G22D
- Merge fixes from stable versions 4.4.139-4.4.154 inclusive
- Fix some stable regressions
I also tagged two intermediate versions:
-?4.4.138-cip26: before merging from 4.4-stable
- 4.4.154-cip27: missing R8A7745 sound support (which I accidentally
dropped while rebasing)
Apologies for the long wait.
Ben.
--
Ben Hutchings, Software Developer ? Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
next reply other threads:[~2018-09-12 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 20:25 Ben Hutchings [this message]
2018-09-19 15:59 ` [cip-dev] Linux 4.4.154-cip28 Agustín Benito Bethencourt
2018-09-19 16:48 ` Ben Hutchings
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=1536783932.3024.208.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