All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org
Subject: Re: [E1000-devel] [PATCH] [2.6.26 / RFC] e1000: remove PCI Express device IDs
Date: Fri, 04 Apr 2008 04:08:31 -0400	[thread overview]
Message-ID: <47F5E1FF.4030005@garzik.org> (raw)
In-Reply-To: <47F12E2C.9010800@intel.com>

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@intel.com>
>>> Cc: Linus Torvalds <torvalds@linux-foundation.org>
>>> Cc: Jeff Garzik <jeff@garzik.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"

      reply	other threads:[~2008-04-04  8:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 17:41 [PATCH] [2.6.26 / RFC] e1000: remove PCI Express device IDs Auke Kok
2008-03-29  2:17 ` Jeff Garzik
2008-03-31 18:32   ` [E1000-devel] " Kok, Auke
2008-04-04  8:08     ` Jeff Garzik [this message]

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=47F5E1FF.4030005@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=auke-jan.h.kok@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.