From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: linux-kernel@vger.kernel.org, jeff@garzik.org
Cc: mm-commits@vger.kernel.org, randy.dunlap@oracle.com,
auke-jan.h.kok@intel.com
Subject: Re: + e1000e-make-e1000e-default-to-the-same-kconfig-setting-as-e1000.patch added to -mm tree
Date: Tue, 11 Dec 2007 15:31:58 -0800 [thread overview]
Message-ID: <475F1DEE.4080909@intel.com> (raw)
In-Reply-To: <200712112328.lBBNSUN6014553@imap1.linux-foundation.org>
akpm@linux-foundation.org wrote:
> The patch titled
> e1000e: make E1000E default to the same kconfig setting as E1000
> has been added to the -mm tree. Its filename is
> e1000e-make-e1000e-default-to-the-same-kconfig-setting-as-e1000.patch
>
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
> See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
> out what to do about this
>
> ------------------------------------------------------
> Subject: e1000e: make E1000E default to the same kconfig setting as E1000
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Make E1000E default to the same kconfig setting as E1000. So people's
> machiens don't stop working when they use oldconfig.
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: Jeff Garzik <jeff@garzik.org>
> Cc: Auke Kok <auke-jan.h.kok@intel.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/net/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff -puN drivers/net/Kconfig~e1000e-make-e1000e-default-to-the-same-kconfig-setting-as-e1000 drivers/net/Kconfig
> --- a/drivers/net/Kconfig~e1000e-make-e1000e-default-to-the-same-kconfig-setting-as-e1000
> +++ a/drivers/net/Kconfig
> @@ -1986,6 +1986,7 @@ config E1000_DISABLE_PACKET_SPLIT
> config E1000E
> tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
> depends on PCI
> + default E1000
> ---help---
> This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
> ethernet family of adapters. For PCI or PCI-X e1000 adapters,
Acked-by: Auke Kok <auke-jan.h.kok@intel.com>
Jeff, can you apply to #upstream?
Auke
parent reply other threads:[~2007-12-11 23:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200712112328.lBBNSUN6014553@imap1.linux-foundation.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=475F1DEE.4080909@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox