lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151201062218.GD16260@verge.net.au>
Date:	Tue, 1 Dec 2015 15:22:19 +0900
From:	Simon Horman <horms@...ge.net.au>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Linux-sh list <linux-sh@...r.kernel.org>,
	Rob Herring <robh+dt@...nel.org>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH] ravb: add R8A7791 support

On Mon, Nov 30, 2015 at 09:08:57AM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
> 
> On Mon, Nov 30, 2015 at 1:42 AM, Simon Horman <horms@...ge.net.au> wrote:
> > On Mon, Nov 30, 2015 at 12:14:21AM +0300, Sergei Shtylyov wrote:
> >> 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.
> 
> You're aware we have to keep the existing SoC-specific ones in the driver,
> for backwards compatibility?

Yes, I am aware of that.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ