From: Rob Herring <robh@kernel.org>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Magnus Damm <magnus.damm@gmail.com>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH can-next 2/2] CAN: rcar: add device tree support for r8a779[234]
Date: Sun, 21 Feb 2016 21:36:44 -0600 [thread overview]
Message-ID: <20160222033644.GB24277@rob-hp-laptop> (raw)
In-Reply-To: <1456107350-12100-3-git-send-email-horms+renesas@verge.net.au>
On Mon, Feb 22, 2016 at 11:15:50AM +0900, Simon Horman wrote:
> Simply document new compatibility string.
> As a previous patch adds a generic R-Car Gen2 compatibility string
> there appears to be no need for a driver updates.
>
> By documenting this compat sting it may be used in DTSs shipped, for
> example as part of ROMs. It must be used in conjunction with the Gen2
> fallback compat string. At this time there are no known differences between
> the r8a779[234] IP blocks and that implemented by the driver for the Gen2
> fallback compat string. Thus there is no need to update the driver as the
> use of the Gen2 fallback compat string will activate the correct code in
> the current driver while leaving the option for r8a779[234]-specific driver
> code to be activated in an updated driver should the need arise.
>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> ---
> Documentation/devicetree/bindings/net/can/rcar_can.txt | 3 +++
> drivers/net/can/rcar_can.c | 3 +++
> 2 files changed, 6 insertions(+)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-02-22 3:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 2:15 [PATCH can-next 0/2] CAN: rcar: add fallback and r8a779[234] bindings Simon Horman
2016-02-22 2:15 ` [PATCH can-next 1/2] CAN: rcar: add gen[12] fallback compatibility strings Simon Horman
2016-02-22 3:37 ` Rob Herring
2016-02-22 9:40 ` Marc Kleine-Budde
2016-02-23 0:08 ` Simon Horman
2016-02-22 15:40 ` Geert Uytterhoeven
2016-02-23 0:03 ` Simon Horman
2016-02-22 2:15 ` [PATCH can-next 2/2] CAN: rcar: add device tree support for r8a779[234] Simon Horman
2016-02-22 3:36 ` Rob Herring [this message]
2016-02-22 13:48 ` Geert Uytterhoeven
2016-02-23 0:02 ` 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=20160222033644.GB24277@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=mkl@pengutronix.de \
--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).