From: Simon Horman <horms@verge.net.au>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] ravb: add R8A7791 support
Date: Mon, 30 Nov 2015 09:42:08 +0900 [thread overview]
Message-ID: <20151130004207.GD3501@verge.net.au> (raw)
In-Reply-To: <565B6AAD.8080205@cogentembedded.com>
On Mon, Nov 30, 2015 at 12:14:21AM +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 11/29/2015 10:26 PM, Geert Uytterhoeven wrote:
>
> >>Add support for yet another ARM member of the R-Car family, R-Car M2, also
>
> >R-Car M2-W?
>
> Right, forgot about the postfixes.
>
> >>known as R8A7791.
> >
> >There's also R-Car M2-N, aka R8A7793, but you probably know that ;-)
>
> Will fix.
I would prefer if we added generic gen2 and gen3 compat strings to the driver
and only documented new soc-specific compat strings.
Actually by chance I was planning to up patches to do that and add compat
strings for the missing Gen2 boards. But I won't complain if you beat me to
it.
next prev parent reply other threads:[~2015-11-30 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 22:06 [PATCH] ravb: add R8A7791 support Sergei Shtylyov
[not found] ` <6051623.qN4lqSyZKg-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2015-11-29 19:26 ` Geert Uytterhoeven
2015-11-29 21:14 ` Sergei Shtylyov
2015-11-30 0:42 ` Simon Horman [this message]
2015-11-30 8:08 ` Geert Uytterhoeven
2015-12-01 6:22 ` Simon Horman
2015-11-30 19:08 ` Sergei Shtylyov
2015-12-01 6:24 ` 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=20151130004207.GD3501@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=geert@linux-m68k.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-sh@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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).