From: Jeff Garzik <jeff@garzik.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RESEND PATCH 2/3] e1000: remove PCI Express device IDs
Date: Fri, 27 Jun 2008 02:08:14 -0400 [thread overview]
Message-ID: <486483CE.8010305@garzik.org> (raw)
In-Reply-To: <20080622222021.5907.16668.stgit@localhost.localdomain>
Jeff Kirsher wrote:
> From: Auke Kok <auke-jan.h.kok@intel.com>
>
> 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@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Cc: Jeff Garzik <jeff@garzik.org>
> ---
>
> drivers/net/Kconfig | 3 ---
> drivers/net/e1000/e1000_main.c | 33 ---------------------------------
> 2 files changed, 0 insertions(+), 36 deletions(-)
applied to #upstream-next (queued for 2.6.27)
BIG FLASHING WARNING NOTE to x86 maintainers and others:
Make sure your defconfig changes are in place for this change.
next prev parent reply other threads:[~2008-06-27 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 22:20 [RESEND PATCH 1/3] e1000e: set CONFIG_E1000E=y in x86 defconfigs Jeff Kirsher
2008-06-22 22:21 ` [RESEND PATCH 2/3] e1000: remove PCI Express device IDs Jeff Kirsher
2008-06-27 6:08 ` Jeff Garzik [this message]
2008-06-22 22:22 ` [RESEND PATCH 3/3] e1000: enable NAPI by default in defconfig Jeff Kirsher
2008-06-23 11:26 ` [RESEND PATCH 1/3] e1000e: set CONFIG_E1000E=y in x86 defconfigs Ingo Molnar
2008-06-23 23:14 ` Jeff Kirsher
2008-06-23 23:20 ` Jeff Garzik
2008-06-26 12:39 ` Ingo Molnar
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=486483CE.8010305@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).