The patch titled
sis5513: add SiS south bridge ID 0x966 and 0x968
has been removed from the -mm tree. Its filename is
sis5513-add-sis-south-bridge-id-0x966.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: sis5513: add SiS south bridge ID 0x966 and 0x968
From: David Wang <touch@xxxxxxx>
New SiS south bridge device ID is 0x966.
Next coming product will be 0x968. (Will be released in Q4, this year)
We don't make any updates to the IDE controller.
Signed-off-by: David Wang <touch@xxxxxxx>
Cc: Jeff Garzik <jeff@xxxxxxxxxx>
Cc: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
drivers/ide/pci/sis5513.c | 2 ++
include/linux/pci_ids.h | 2 ++
2 files changed, 4 insertions(+)
diff -puN drivers/ide/pci/sis5513.c~sis5513-add-sis-south-bridge-id-0x966 drivers/ide/pci/sis5513.c
--- a/drivers/ide/pci/sis5513.c~sis5513-add-sis-south-bridge-id-0x966
+++ a/drivers/ide/pci/sis5513.c
@@ -86,6 +86,8 @@ static const struct {
u8 chipset_family;
u8 flags;
} SiSHostChipInfo[] = {
+ { "SiS968", PCI_DEVICE_ID_SI_968, ATA_133 },
+ { "SiS966", PCI_DEVICE_ID_SI_966, ATA_133 },
{ "SiS965", PCI_DEVICE_ID_SI_965, ATA_133 },
{ "SiS745", PCI_DEVICE_ID_SI_745, ATA_100 },
{ "SiS735", PCI_DEVICE_ID_SI_735, ATA_100 },
diff -puN include/linux/pci_ids.h~sis5513-add-sis-south-bridge-id-0x966 include/linux/pci_ids.h
--- a/include/linux/pci_ids.h~sis5513-add-sis-south-bridge-id-0x966
+++ a/include/linux/pci_ids.h
@@ -648,6 +648,8 @@
#define PCI_DEVICE_ID_SI_962 0x0962
#define PCI_DEVICE_ID_SI_963 0x0963
#define PCI_DEVICE_ID_SI_965 0x0965
+#define PCI_DEVICE_ID_SI_966 0x0966
+#define PCI_DEVICE_ID_SI_968 0x0968
#define PCI_DEVICE_ID_SI_5511 0x5511
#define PCI_DEVICE_ID_SI_5513 0x5513
#define PCI_DEVICE_ID_SI_5517 0x5517
_
Patches currently in -mm which might be from touch@xxxxxxx are
origin.patch
git-libata-all.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
