netdev - Re: [PATCH net-next,V2] Add LAN9352 Ethernet Driver

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]

Date:	Tue, 16 Feb 2016 16:38:57 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	Bryan.Whitehead@...rochip.com
Cc:	andrew@...n.ch, f.fainelli@...il.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next,V2] Add LAN9352 Ethernet Driver

From: <Bryan.Whitehead@...rochip.com>
Date: Tue, 16 Feb 2016 21:32:20 +0000

> I just spoke with my manager, and we would like to change the target
> device from LAN9352 to LAN9250. The LAN9250 is the same as the
> LAN9352 but without the switch. It has one mac and one phy.
> 
> Since there is no switch in that product, will that make a pure
> Ethernet driver easier to accept?

I'm not going to allow you to weasel away from doing things correctly
by doing this.

You are doing this so you can still put the pure ethernet driver into
the tree, and then off-tree you'll just add the device ID for the
switch device.

Sorry, that won't pass.