From: David Miller <davem@davemloft.net>
To: auke-jan.h.kok@intel.com
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
jesse.brandeburg@intel.com, jeff@garzik.org
Subject: Re: [PATCH] e1000e: test MSI interrupts
Date: Thu, 27 Mar 2008 17:03:50 -0700 (PDT) [thread overview]
Message-ID: <20080327.170350.113054010.davem@davemloft.net> (raw)
In-Reply-To: <47EC3393.5010901@intel.com>
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
Date: Thu, 27 Mar 2008 16:53:55 -0700
> the only alternative I see is that we have a quirk in the e1000
> driver that acts when the combination of an 82571 and this
> particular chipset is found, but I have no information ATM on the
> chipset id's yet and on how to identify this configuration.
And this is how you will fix this bug, once you know these
IDs.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
next prev parent reply other threads:[~2008-03-28 0:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 18:36 [PATCH] e1000e: test MSI interrupts Auke Kok
2008-03-26 18:42 ` Jeff Garzik
2008-03-26 20:42 ` [E1000-devel] " Kok, Auke
2008-03-27 17:53 ` Brandeburg, Jesse
2008-03-27 19:43 ` Jeff Garzik
2008-03-27 22:05 ` David Miller
2008-03-27 22:55 ` Brandeburg, Jesse
2008-03-27 23:06 ` David Miller
2008-03-27 23:38 ` Jeff Garzik
2008-03-27 23:53 ` Kok, Auke
2008-03-28 0:03 ` David Miller [this message]
2008-03-27 21:59 ` David Miller
2008-03-27 22:05 ` Andy Gospodarek
2008-03-27 22:16 ` Kok, Auke
2008-03-27 22:33 ` Andy Gospodarek
2008-03-27 22:47 ` Kok, Auke
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=20080327.170350.113054010.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=auke-jan.h.kok@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeff@garzik.org \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.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 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).