From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms+renesas@verge.net.au>,
netdev@vger.kernel.org, linux-sh@vger.kernel.org
Cc: Magnus Damm <magnus.damm@gmail.com>, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2 net-next] ravb: Add fallback compatibility strings
Date: Tue, 1 Dec 2015 13:26:08 +0300 [thread overview]
Message-ID: <565D75C0.1020502@cogentembedded.com> (raw)
In-Reply-To: <1448955783-22806-2-git-send-email-horms+renesas@verge.net.au>
Hello.
On 12/1/2015 10:43 AM, Simon Horman 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.
Why?
[...]
MBR, Sergei
next prev parent reply other threads:[~2015-12-01 10:26 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
2015-12-01 10:26 ` Sergei Shtylyov [this message]
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=565D75C0.1020502@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.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).