linux-kernel - Re: [GIT]: Networking

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: <20080509.144359.194792251.davem@davemloft.net>
Date:	Fri, 09 May 2008 14:43:59 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	torvalds@...ux-foundation.org
Cc:	jeff@...zik.org, akpm@...ux-foundation.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT]: Networking

From: Linus Torvalds <torvalds@...ux-foundation.org>
Date: Fri, 9 May 2008 08:05:47 -0700 (PDT)

> On Fri, 9 May 2008, Jeff Garzik wrote:
> > 
> > The e1000e change is just a bunch of code additions for a new phy type, not a
> > bunch of /changes/ really.  Is that the change you're concerned with?
> 
> Yes. I saw 800 new lines to a driver I use, and I go "Ugh".

And if it enabled support for a device you have, for which you've been
patching the driver for some time, you'd go "Yippie!" :-)))

BTW, this reminds me, did we get that driver in for the device the
EEPC machines use?  I have this strange feeling like that slipped
through the cracks.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/