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]

Date:	Tue, 21 Oct 2008 19:48:38 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Catalin Marinas <catalin.marinas@....com>
Cc:	Steve.Glendinning@...c.com, Bill Gatliff <bgat@...lgatliff.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

On Tue, Oct 21, 2008 at 11:42:06AM +0100, Catalin Marinas wrote:
> 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.

There has been several concerted efforts to eliminating one or other.
The problem is that eepro100.c works on some platform/chip combinations
that e100.c doesn't and, probably, vice versa.  So, removing either
causes people regressions.

That's the problem with merging two drivers, and then trying to remove
one later - the hardware they support diverges and then you need to
keep and maintain both.
--
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