From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC Drivers Updates for v4.12
Date: Tue, 21 Mar 2017 17:37:50 -0700 [thread overview]
Message-ID: <20170322003750.GI5129@localhost> (raw)
In-Reply-To: <cover.1490000158.git.horms+renesas@verge.net.au>
On Mon, Mar 20, 2017 at 09:58:23AM +0100, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these Renesas ARM based SoC drivers updates for v4.12.
>
>
> The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:
>
> Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-drivers-for-v4.12
>
> for you to fetch changes up to cd59de80dd34dd2d1a3ca97d7a6e712c048b135a:
>
> soc: renesas: Identify RZ/G1N (2017-03-13 10:26:08 +0100)
>
> ----------------------------------------------------------------
> Renesas ARM Based SoC Drivers Updates for v4.12
>
> * Identify RZ/G1N and RZ/G1H
>
> ----------------------------------------------------------------
> Geert Uytterhoeven (2):
> soc: renesas: Identify RZ/G1H
> soc: renesas: Identify RZ/G1N
At first I was wondering why you'd applied the same patch twice. Renesas likes
to make names similar *and* hard to remember sometimes. :-)
-Olof
next prev parent reply other threads:[~2017-03-22 0:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 8:58 [GIT PULL] Renesas ARM Based SoC Drivers Updates for v4.12 Simon Horman
2017-03-20 8:58 ` [PATCH 1/2] soc: renesas: Identify RZ/G1H Simon Horman
2017-03-20 8:58 ` [PATCH 2/2] soc: renesas: Identify RZ/G1N Simon Horman
2017-03-22 0:37 ` Olof Johansson [this message]
2017-03-24 6:52 ` [GIT PULL] Renesas ARM Based SoC Drivers Updates for v4.12 Simon Horman
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=20170322003750.GI5129@localhost \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).