From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>, linux-pci@vger.kernel.org
Subject: [PATCH v2 0/6] pci.h/pci_ids.h related cleanups
Date: Mon, 30 Mar 2015 12:59:21 +0200 [thread overview]
Message-ID: <1427712964-16155-1-git-send-email-mst@redhat.com> (raw)
A bunch of drivers pull in linux/pci.h or linux/pci_ids.h without actually
using any PCI APIs.
Clean this up, drop the includes.
These patches were split out from bigger pci_ids.h exporting patchset.
I think the pci tree is easiest to use for these changes.
Please review, and consider for 4.1.
Changes from v1:
patches are unchanged
drop amd patch - applied on driver specific tree
added acks for brcm80211
Michael S. Tsirkin (6):
crypto/ccp: drop linux/pci dependencies
input/serio: drop pci_ids dependency
media/fintek: drop pci_ids dependency
brcm80211: drop pci dependency
brcm80211: drop pci_ids include
staging/olpc: drop pci dependencies
drivers/crypto/ccp/ccp-ops.c | 2 --
drivers/input/serio/gscps2.c | 1 -
drivers/media/rc/fintek-cir.c | 1 -
drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c | 2 --
drivers/net/wireless/brcm80211/brcmfmac/sdio.c | 1 -
drivers/staging/olpc_dcon/olpc_dcon.c | 2 --
6 files changed, 9 deletions(-)
--
MST
next reply other threads:[~2015-03-30 10:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 10:59 Michael S. Tsirkin [this message]
2015-03-30 10:59 ` [PATCH v2 1/6] crypto/ccp: drop linux/pci dependencies Michael S. Tsirkin
2015-03-30 10:59 ` [PATCH v2 2/6] input/serio: drop pci_ids dependency Michael S. Tsirkin
2015-04-06 16:24 ` Dmitry Torokhov
2015-03-30 10:59 ` [PATCH v2 3/6] media/fintek: " Michael S. Tsirkin
2015-03-30 12:17 ` Mauro Carvalho Chehab
2015-03-30 10:59 ` [PATCH v2 4/6] brcm80211: drop pci dependency Michael S. Tsirkin
2015-03-30 10:59 ` [PATCH v2 5/6] brcm80211: drop pci_ids include Michael S. Tsirkin
2015-03-30 10:59 ` [PATCH v2 6/6] staging/olpc: drop pci dependencies Michael S. Tsirkin
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=1427712964-16155-1-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 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).