From: Roland Dreier <roland@topspin.com>
To: "Narendra Sankar" <nsankar@broadcom.com>
Cc: "David S. Miller" <davem@davemloft.net>,
gregkh@suse.de, torvalds@osdl.org, akpm@osdl.org,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [GIT PATCH] Another PCI fix for 2.6.12-rc6
Date: Thu, 09 Jun 2005 15:55:06 -0700 [thread overview]
Message-ID: <52zmtz16ph.fsf@topspin.com> (raw)
In-Reply-To: <42A8C73C.6060005@broadcom.com> (Narendra Sankar's message of "Thu, 09 Jun 2005 15:48:28 -0700")
Narendra> So it would still be useful to have this patch in, would
Narendra> it not?
Yes, we should use the PCI quirk to disable MSI when we know a host
bridge does not support MSI.
- R.
prev parent reply other threads:[~2005-06-09 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 22:20 [GIT PATCH] Another PCI fix for 2.6.12-rc6 Greg KH
2005-06-09 22:21 ` [PATCH] PCI: MSI functionality broken on Serverworks GC chipset Greg KH
2005-06-09 22:31 ` David S. Miller
2005-06-09 22:32 ` [GIT PATCH] Another PCI fix for 2.6.12-rc6 David S. Miller
2005-06-09 22:48 ` Narendra Sankar
2005-06-09 22:51 ` David S. Miller
2005-06-09 22:56 ` Narendra Sankar
2005-06-09 22:55 ` Roland Dreier [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=52zmtz16ph.fsf@topspin.com \
--to=roland@topspin.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=nsankar@broadcom.com \
--cc=torvalds@osdl.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