netdev - Re: [RESEND PATCH 1/3] e1000e: set CONFIG

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: <48602FA8.7090508@garzik.org>
Date:	Mon, 23 Jun 2008 19:20:08 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, davem@...emloft.net
Subject: Re: [RESEND PATCH 1/3] e1000e: set CONFIG_E1000E=y in x86	defconfigs

Ingo Molnar wrote:
> * Jeff Kirsher <jeffrey.t.kirsher@...el.com> wrote:
> 
>> From: Auke Kok <auke-jan.h.kok@...el.com>
>>
>> This adds to the already default CONFIG_E1000=y in these files.
>>
>> Signed-off-by: Auke Kok <auke-jan.h.kok@...el.com>
>> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
>> ---
>>
>>  arch/x86/configs/i386_defconfig   |    1 +
>>  arch/x86/configs/x86_64_defconfig |    1 +
> 
> that is not an e1000 patch but an arch/x86 defconfig patch. NAK on this 
> route of patch propagation.

But it's dependent on an e1000 patch.  Maybe we could follow the lead of 
ppc and other arch maintainers, and work together?

Typically if there are arch dependencies and little drivers/net changes, 
I'll ACK the drivers/net change and then let it go through the arch tree.

In this case, there is far more drivers/net code, so it would make the 
most sense to work with you to change the defconfigs to your liking, and 
then merge them via netdev when the other E1000 changes go in.

	Jeff

--
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