linux-kernel - 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: <20080626123950.GR29619@elte.hu>
Date:	Thu, 26 Jun 2008 14:39:50 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeff Garzik <jeff@...zik.org>
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


* Jeff Garzik <jeff@...zik.org> wrote:

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

the normal flow for defconfig changes is to first do the driver changes, 
then later on propagate anything that is needed into the defconfig, once 
the driver change is upstream.

for example we've already got this queued up in tip/x86:

| commit b5d958ea66ac11b1190c24f042f517adf9229a98
| Author: Auke Kok <auke-jan.h.kok@...el.com>
| Date:   Wed Apr 9 13:17:39 2008 -0700
|
|    e1000e: set CONFIG_E1000E=y in x86 defconfigs
|
|    This adds to the already default CONFIG_E1000=y in these files.

and there's a fair number of other changes as well to the defconfigs for 
v2.6.27 which might collide. So it would be nice to keep it separate 
please.

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