netdev - Re: [PATCH 14/16] RealView: Use the in-kernel smc911x.c driver on RealView

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: <48FDD852.7080104@billgatliff.com>
Date:	Tue, 21 Oct 2008 08:25:38 -0500
From:	Bill Gatliff <bgat@...lgatliff.com>
To:	Catalin Marinas <catalin.marinas@....com>
CC:	Steve.Glendinning@...c.com,
	Guennadi Liakhovetski <g.liakhovetski@....de>,
	linux-arm-kernel@...ts.arm.linux.org.uk, Ian.Saturley@...c.com,
	netdev@...r.kernel.org
Subject: Re: [PATCH 14/16] RealView: Use the in-kernel smc911x.c driver	on
 RealView

Catalin Marinas wrote:
> On Tue, 2008-10-21 at 11:26 +0100, Steve.Glendinning@...c.com wrote:
>> The smsc911x driver is still maintained (out of tree), and is used by many
>> of our customers.  Mainline inclusion is still very much the intention!
>>
>> Almost all the feedback I've had has been positive, but I've had a few
>> "can't you just fix the in-tree driver?" responses.  The trouble is it's
>> not a *small* piece of work!
> 
> Can we not have both drivers in the kernel until the transition to the
> new one has finished? We seem to still have both eepro100.c and e100.c
> in the kernel targeting similar chips.

I don't have a problem with that.  I have standardized my kernels on Steve's
driver, though, in anticipation of the transition.  So you know which one I'll
advocate for.  :)


b.g.
-- 
Bill Gatliff
bgat@...lgatliff.com
--
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