From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
<ebiederm@xmission.com>, Michael Chan <mchan@broadcom.com>,
Jean Pierre Dion <jean-pierre.dion@bull.net>
Subject: [PATCH -mm] remove HT1000 from the quirk_msi_ht_cap quirk
Date: Wed, 28 Nov 2007 15:47:28 +0100 [thread overview]
Message-ID: <20071128154728.109664a2@bull.net> (raw)
Andrew, due to mailer problems, I'm not sure you received my previous mail
titled: "[PATCH] V2 - quirk: Enable MSI Mapping on HT1000" if you did,
then forget it and use this one instead. Or if you already merged V2 then
drop this one.
Sorry for the inconvenience.
Sebastien.
From: Sebastien Dugue <sebastien.dugue@bull.net>
Now that the HyperTransport MSI mapping capability is enabled for Broadcom's
HT1000 bridge, the quirk_msi_ht_cap quirk is no longer necessary.
Signed-off-by: Sebastien Dugue <sebastien.dugue@bull.net>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Michael Chan <mchan@broadcom.com>
---
drivers/pci/quirks.c | 4 ----
1 file changed, 4 deletions(-)
Index: linux-2.6.24-rc3-mm2/drivers/pci/quirks.c
===================================================================
--- linux-2.6.24-rc3-mm2.orig/drivers/pci/quirks.c
+++ linux-2.6.24-rc3-mm2/drivers/pci/quirks.c
@@ -1711,10 +1711,6 @@ static void __devinit quirk_msi_ht_cap(s
}
DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_SERVERWORKS, PCI_DEVICE_ID_SERVERWORKS_HT2000_PCIE,
quirk_msi_ht_cap);
-DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_SERVERWORKS,
- PCI_DEVICE_ID_SERVERWORKS_HT1000_PXB,
- quirk_msi_ht_cap);
-
/*
* Force enable MSI mapping capability on HT bridges
reply other threads:[~2007-11-28 14:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20071128154728.109664a2@bull.net \
--to=sebastien.dugue@bull.net \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=jean-pierre.dion@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
/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
all inboxes | Powered by JetHome®