* [PATCH 1/3] pci_ids: put Hudson-2 device IDs together
@ 2013-05-31 11:17 Shane Huang
2013-05-31 3:33 ` Tejun Heo
2013-05-31 6:05 ` Jean Delvare
0 siblings, 2 replies; 3+ messages in thread
From: Shane Huang @ 2013-05-31 11:17 UTC (permalink / raw)
To: Bjorn Helgaas
Cc: Tejun Heo, Jean Delvare, linux-pci, linux-ide, linux-i2c,
Shane Huang
To put all AMD Hudson-2 device IDs together for better maintenance.
Signed-off-by: Shane Huang <shane.huang@amd.com>
---
include/linux/pci_ids.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index c129162..e0b5623 100644
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_ids.h
@@ -556,7 +556,6 @@
#define PCI_DEVICE_ID_AMD_8131_BRIDGE 0x7450
#define PCI_DEVICE_ID_AMD_8131_APIC 0x7451
#define PCI_DEVICE_ID_AMD_8132_BRIDGE 0x7458
-#define PCI_DEVICE_ID_AMD_HUDSON2_SMBUS 0x780b
#define PCI_DEVICE_ID_AMD_CS5535_IDE 0x208F
#define PCI_DEVICE_ID_AMD_CS5536_ISA 0x2090
#define PCI_DEVICE_ID_AMD_CS5536_FLASH 0x2091
@@ -570,6 +569,7 @@
#define PCI_DEVICE_ID_AMD_LX_AES 0x2082
#define PCI_DEVICE_ID_AMD_HUDSON2_IDE 0x780c
#define PCI_DEVICE_ID_AMD_HUDSON2_SATA_IDE 0x7800
+#define PCI_DEVICE_ID_AMD_HUDSON2_SMBUS 0x780b
#define PCI_VENDOR_ID_TRIDENT 0x1023
#define PCI_DEVICE_ID_TRIDENT_4DWAVE_DX 0x2000
--
1.8.1.2
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH 1/3] pci_ids: put Hudson-2 device IDs together
2013-05-31 11:17 [PATCH 1/3] pci_ids: put Hudson-2 device IDs together Shane Huang
@ 2013-05-31 3:33 ` Tejun Heo
2013-05-31 6:05 ` Jean Delvare
1 sibling, 0 replies; 3+ messages in thread
From: Tejun Heo @ 2013-05-31 3:33 UTC (permalink / raw)
To: Shane Huang; +Cc: Bjorn Helgaas, Jean Delvare, linux-pci, linux-ide, linux-i2c
On Fri, May 31, 2013 at 07:17:19PM +0800, Shane Huang wrote:
> To put all AMD Hudson-2 device IDs together for better maintenance.
>
> Signed-off-by: Shane Huang <shane.huang@amd.com>
Bjorn, how should we route these patches? The second will conflict
with the first. If it's okay, I can take the first two through libata
tree.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 1/3] pci_ids: put Hudson-2 device IDs together
2013-05-31 11:17 [PATCH 1/3] pci_ids: put Hudson-2 device IDs together Shane Huang
2013-05-31 3:33 ` Tejun Heo
@ 2013-05-31 6:05 ` Jean Delvare
1 sibling, 0 replies; 3+ messages in thread
From: Jean Delvare @ 2013-05-31 6:05 UTC (permalink / raw)
To: Shane Huang; +Cc: Bjorn Helgaas, Tejun Heo, linux-pci, linux-ide, linux-i2c
On Fri, 31 May 2013 19:17:19 +0800, Shane Huang wrote:
> To put all AMD Hudson-2 device IDs together for better maintenance.
>
> Signed-off-by: Shane Huang <shane.huang@amd.com>
> ---
> include/linux/pci_ids.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> index c129162..e0b5623 100644
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -556,7 +556,6 @@
> #define PCI_DEVICE_ID_AMD_8131_BRIDGE 0x7450
> #define PCI_DEVICE_ID_AMD_8131_APIC 0x7451
> #define PCI_DEVICE_ID_AMD_8132_BRIDGE 0x7458
> -#define PCI_DEVICE_ID_AMD_HUDSON2_SMBUS 0x780b
> #define PCI_DEVICE_ID_AMD_CS5535_IDE 0x208F
> #define PCI_DEVICE_ID_AMD_CS5536_ISA 0x2090
> #define PCI_DEVICE_ID_AMD_CS5536_FLASH 0x2091
> @@ -570,6 +569,7 @@
> #define PCI_DEVICE_ID_AMD_LX_AES 0x2082
> #define PCI_DEVICE_ID_AMD_HUDSON2_IDE 0x780c
> #define PCI_DEVICE_ID_AMD_HUDSON2_SATA_IDE 0x7800
> +#define PCI_DEVICE_ID_AMD_HUDSON2_SMBUS 0x780b
>
> #define PCI_VENDOR_ID_TRIDENT 0x1023
> #define PCI_DEVICE_ID_TRIDENT_4DWAVE_DX 0x2000
Acked-by: Jean Delvare <khali@linux-fr.org>
--
Jean Delvare
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-05-31 6:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-05-31 11:17 [PATCH 1/3] pci_ids: put Hudson-2 device IDs together Shane Huang
2013-05-31 3:33 ` Tejun Heo
2013-05-31 6:05 ` Jean Delvare
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).