netdev - Re: [E1000-devel] [PATCH] [2.6.26 / RFC] e1000: remove PCI Express device IDs

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] [day] [month] [year] [list]

Date:	Fri, 04 Apr 2008 04:08:31 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	"Kok, Auke" <auke-jan.h.kok@...el.com>
CC:	e1000-devel@...ts.sourceforge.net, netdev@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org
Subject: Re: [E1000-devel] [PATCH] [2.6.26 / RFC] e1000: remove PCI Express
 device IDs

Kok, Auke wrote:
> Jeff Garzik wrote:
>> Auke Kok wrote:
>>> We do not want to prolong the situation much longer that e1000
>>> and e1000e support these devices at the same time. As a result,
>>> take out the bandage that was added for the interim period
>>> and remove all the PCI Express device IDs from e1000.
>>>
>>> Signed-off-by: Auke Kok <auke-jan.h.kok@...el.com>
>>> Cc: Linus Torvalds <torvalds@...ux-foundation.org>
>>> Cc: Jeff Garzik <jeff@...zik.org>
>>> ---
>>>
>>>  drivers/net/Kconfig            |    3 ---
>>>  drivers/net/e1000/e1000_main.c |   33 ---------------------------------
>>>  2 files changed, 0 insertions(+), 36 deletions(-)
>> I'm certainly fine with this for 2.6.26.
>>
>> Do we need to make a public "move to e1000e" announcement, or were the 
>> previous threads sufficient?  :)
> 
> I'm OK with that and will write one such thing to lkml+netdev during the next
> merge window. ok?

I'd say write one sooner rather than later... :)  "this is coming"
--
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