netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jesse.brandeburg@intel.com
Cc: auke-jan.h.kok@intel.com, jeff@garzik.org,
	e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH] e1000e: test MSI interrupts
Date: Thu, 27 Mar 2008 14:59:59 -0700 (PDT)	[thread overview]
Message-ID: <20080327.145959.64040869.davem@davemloft.net> (raw)
In-Reply-To: <36D9DB17C6DE9E40B059440DB8D95F5204BF07F7@orsmsx418.amr.corp.intel.com>

From: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Date: Thu, 27 Mar 2008 10:53:43 -0700

> >> The platforms with MSI problems should be discovered, made public,
> >> and worked around. 
> 
> This is our workaround, it is our fault, the incompatible chipset is in
> an x3850 IBM system.

Then you look for that system chipset variant in the e1000e driver and
not use MSI when it is found.

A generic test really is not warranted.

  parent reply	other threads:[~2008-03-27 21:59 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
2008-03-27 21:59       ` David Miller [this message]
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.145959.64040869.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).