From: Richard Leitner <dev@g0hl1n.net>
To: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Cc: gregkh@linuxfoundation.org, mathias.nyman@intel.com,
bhelgaas@google.com, richard.leitner@skidata.com
Subject: [PATCH 0/3] usb: host: pci: PCI ID consolidation
Date: Wed, 14 Mar 2018 11:29:30 +0100 [thread overview]
Message-ID: <20180314102933.21367-1-dev@g0hl1n.net> (raw)
From: Richard Leitner <richard.leitner@skidata.com>
Centralize some hardcoded PCI IDs as definitions in the global
include/linux/pci_ids.h file. This is done to reduce the amount of
scattered PCI ID definitions and hardcoded values across the kernel.
Richard Leitner (3):
usb: host: pci: use existing Intel PCI ID macros
usb: host: pci: introduce PCI vendor ID for Netlogic
usb: host: pci: replace hardcoded renesas PCI IDs
drivers/usb/host/pci-quirks.c | 16 +++++++++-------
drivers/usb/host/xhci-pci.c | 7 ++++---
include/linux/pci_ids.h | 5 +++++
3 files changed, 18 insertions(+), 10 deletions(-)
--
2.11.0
next reply other threads:[~2018-03-14 10:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 10:29 Richard Leitner [this message]
2018-03-14 10:29 ` [PATCH 1/3] usb: host: pci: use existing Intel PCI ID macros Richard Leitner
2018-03-14 10:48 ` Greg KH
2018-03-14 10:29 ` [PATCH 2/3] usb: host: pci: introduce PCI vendor ID for Netlogic Richard Leitner
2018-03-14 10:48 ` Greg KH
2018-03-14 11:36 ` Richard Leitner
2018-03-14 11:49 ` Greg KH
2018-03-14 12:17 ` Oliver Neukum
2018-03-14 13:31 ` Richard Leitner
2018-03-14 15:27 ` Oliver Neukum
2018-03-14 15:44 ` Richard Leitner
2018-03-15 9:26 ` Oliver Neukum
2018-03-15 9:47 ` Richard Leitner
2018-03-14 10:29 ` [PATCH 3/3] usb: host: pci: replace hardcoded renesas PCI IDs Richard Leitner
2018-03-14 10:49 ` Greg KH
2018-03-14 11:38 ` Richard Leitner
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=20180314102933.21367-1-dev@g0hl1n.net \
--to=dev@g0hl1n.net \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=richard.leitner@skidata.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;
as well as URLs for NNTP newsgroup(s).