From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Simon Horman <horms+renesas@verge.net.au>,
Wolfgang Grandegger <wg@grandegger.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH can-next v2 0/2] CAN: rcar: add fallback and r8a779[234] bindings
Date: Wed, 24 Feb 2016 09:25:20 +0100 [thread overview]
Message-ID: <56CD68F0.8090208@pengutronix.de> (raw)
In-Reply-To: <1456278993-9899-1-git-send-email-horms+renesas@verge.net.au>
[-- Attachment #1: Type: text/plain, Size: 808 bytes --]
On 02/24/2016 02:56 AM, Simon Horman wrote:
> this series adds fallback bindings for R-Car Gen 1 and Gen 2 SoCs and
> SoC-specific bindings for the r8a779[234] SoCs which are R-Car Gen 2 SoCs.
>
> The aim is to provide consistent bindings for R-Car Gen 1 and Gen 2
> SoCs in a maner consistent with that progressively being used
> for drivers for other IP blocks used by Renesas SoCs.
>
> For changes since v1 see individial patch changelogs.
>
> Based on linux-can-next/master
Applied to can-next.
Thanks,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2016-02-24 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 1:56 [PATCH can-next v2 0/2] CAN: rcar: add fallback and r8a779[234] bindings Simon Horman
2016-02-24 1:56 ` [PATCH can-next v2 1/2] CAN: rcar: add gen[12] fallback compatibility strings Simon Horman
2016-02-24 7:36 ` Geert Uytterhoeven
2016-02-24 1:56 ` [PATCH can-next v2 2/2] CAN: rcar: add device tree support for r8a779[234] Simon Horman
2016-02-24 7:35 ` Geert Uytterhoeven
2016-02-24 8:25 ` Marc Kleine-Budde [this message]
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=56CD68F0.8090208@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=horms+renesas@verge.net.au \
--cc=linux-can@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=wg@grandegger.com \
/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).