All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <m.b.lankhorst@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: usb: Move device id for quirk to pci_ids
Date: Sun, 29 May 2011 23:05:34 +0200	[thread overview]
Message-ID: <4DE2B51E.7010807@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 216 bytes --]

Signed-off-by: Maarten Lankhorst <m.b.lankhorst@gmail.com>
---
When adding a quirk for asrock p67 xhci controller I noticed it being 
defined on top, I don't know what the policy is, but shouldn't it be in 
pci_ids?

[-- Attachment #2: 0001-usb-Move-device-id-for-quirk-to-pci_ids.txt --]
[-- Type: text/plain, Size: 1199 bytes --]

>From 9259b45bf91729235e165d584de1a65a09664325 Mon Sep 17 00:00:00 2001
From: Maarten Lankhorst <m.b.lankhorst@gmail.com>
Date: Sun, 29 May 2011 22:56:47 +0200
Subject: [PATCH 1/2] usb: Move device id for quirk to pci_ids

---
 drivers/usb/host/xhci-pci.c |    4 ----
 include/linux/pci_ids.h     |    3 +++
 2 files changed, 3 insertions(+), 4 deletions(-)

diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index a10494c..5a41f05 100644
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
@@ -24,10 +24,6 @@
 
 #include "xhci.h"
 
-/* Device for a quirk */
-#define PCI_VENDOR_ID_FRESCO_LOGIC	0x1b73
-#define PCI_DEVICE_ID_FRESCO_LOGIC_PDK	0x1000
-
 static const char hcd_name[] = "xhci_hcd";
 
 /* called after powerup, by probe or system-pm "wakeup" */
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index 8abe8d7..1c56294 100644
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_ids.h
@@ -2387,6 +2387,9 @@
 
 #define PCI_VENDOR_ID_AZWAVE		0x1a3b
 
+#define PCI_VENDOR_ID_FRESCO_LOGIC	0x1b73
+#define PCI_DEVICE_ID_FRESCO_LOGIC_PDK	0x1000
+
 #define PCI_VENDOR_ID_TEKRAM		0x1de1
 #define PCI_DEVICE_ID_TEKRAM_DC290	0xdc29
 
-- 
1.7.4.1


                 reply	other threads:[~2011-05-29 21:05 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=4DE2B51E.7010807@gmail.com \
    --to=m.b.lankhorst@gmail.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.