From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/2 net-next] ravb: Add fallback compatibility strings
Date: Wed, 2 Dec 2015 09:28:09 +0900 [thread overview]
Message-ID: <20151202002809.GK27457@verge.net.au> (raw)
In-Reply-To: <CAMuHMdW_PagMbAqrvM-_-sJumhMPoYGobNF485Q1D+CRQ5j+bQ@mail.gmail.com>
On Tue, Dec 01, 2015 at 09:42:52AM +0100, Geert Uytterhoeven wrote:
> On Tue, Dec 1, 2015 at 8:43 AM, Simon Horman <horms+renesas@verge.net.au> wrote:
> > Add fallback compatibility strings for R-Car Gen 2 & 3 SoC Families.
> > This is in keeping with the fallback scheme being adopted wherever
> > appropriate for drivers for Renesas SoCs.
> >
> > Also correct typo.
> >
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> > ---
> > Documentation/devicetree/bindings/net/renesas,ravb.txt | 11 +++++++++--
> > drivers/net/ethernet/renesas/ravb_main.c | 2 ++
> > 2 files changed, 11 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/net/renesas,ravb.txt b/Documentation/devicetree/bindings/net/renesas,ravb.txt
> > index b486f3f5f6a3..115006325bff 100644
> > --- a/Documentation/devicetree/bindings/net/renesas,ravb.txt
> > +++ b/Documentation/devicetree/bindings/net/renesas,ravb.txt
> > @@ -1,12 +1,19 @@
> > * Renesas Electronics Ethernet AVB
> >
> > This file provides information on what the device node for the Ethernet AVB
> > -interface contains.
> > +interface.
> >
> > Required properties:
> > - compatible: "renesas,etheravb-r8a7790" if the device is a part of R8A7790 SoC.
> > "renesas,etheravb-r8a7794" if the device is a part of R8A7794 SoC.
> > "renesas,etheravb-r8a7795" if the device is a part of R8A7795 SoC.
> > + "renesas,etheravb-gen2" for generic R-Car Gen 2 compatible interface.
> > + "renesas,etheravb-gen3" for generic R-Car Gen 3 compatible interface.
> > +
>
> (Same comment, different audience)
>
> Shouldn't that be "renesas,etheravb-rcar-gen" or "renesas,etheravb-rcar2"?
>
> Else you'll be in trouble when Renesas starts focussing on airplanes
> (R-Plane Gen2), rockets (R-Rocket Gen2), or IoT (R-IoT Gen2).
Sure, lets go with:
renesas,etheravb-rcar-gen2 and renesas,etheravb-rcar-gen3.
next prev parent reply other threads:[~2015-12-02 0:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 7:43 [PATCH 0/2 net-next] ravb: More compat strings Simon Horman
2015-12-01 7:43 ` [PATCH 1/2 net-next] ravb: Add fallback compatibility strings Simon Horman
2015-12-01 8:42 ` Geert Uytterhoeven
2015-12-02 0:28 ` Simon Horman [this message]
2015-12-01 10:26 ` Sergei Shtylyov
2015-12-02 0:27 ` Simon Horman
2015-12-01 7:43 ` [PATCH 2/2 net-next] ravb: Add device tree support for r8a779[123] 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=20151202002809.GK27457@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).