From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Linux 4.4.126-cip22
Date: Wed, 11 Apr 2018 21:10:37 +0100 [thread overview]
Message-ID: <1523477437.2951.10.camel@codethink.co.uk> (raw)
In-Reply-To: <1523476441.2951.8.camel@codethink.co.uk>
On Wed, 2018-04-11 at 20:54 +0100, Ben Hutchings wrote:
[...]
> I also tagged an intermediate version 4.4.120-cip21 before merging from
> 4.4-stable.
Sorry, that intermediate version was actually 4.4.126-cip21. It
includes the stable changes but not the improvements to Renesas
hardware support that are in -cip22.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
next prev parent reply other threads:[~2018-04-11 20:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 19:54 [cip-dev] Linux 4.4.126-cip22 Ben Hutchings
2018-04-11 20:10 ` Ben Hutchings [this message]
2018-04-27 11:23 ` Daniel Wagner
2018-04-27 11:33 ` Daniel Wagner
2018-04-27 12:10 ` Daniel Wagner
2018-04-27 13:29 ` Daniel Wagner
2018-05-04 14:55 ` Ben Hutchings
[not found] ` <TYAPR01MB228513B0546B4029878033C9B7820@TYAPR01MB2285.jpnprd01.prod.outlook.com>
2018-04-30 10:18 ` Biju Das
2018-05-02 6:35 ` Daniel Wagner
2018-05-02 11:57 ` Biju Das
2018-05-02 13:17 ` Daniel Wagner
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=1523477437.2951.10.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 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.