From: Wei Yang <weiyang@linux.vnet.ibm.com>
To: linux-pci@vger.kernel.org, bhelgaas@google.com
Cc: Wei Yang <weiyang@linux.vnet.ibm.com>
Subject: [PATCH 0/3] PCI: code clean up on pci configuration space
Date: Tue, 14 Oct 2014 14:47:29 +0800 [thread overview]
Message-ID: <1413269253-8990-1-git-send-email-weiyang@linux.vnet.ibm.com> (raw)
This series is a clean up in the pci subsystem when accessing the pci
configuration space.
The first one is to re-use the PCI_FIND_CAP_TTL to limit the times iterating
in pci configuration space.
The next two is to use the exact type to access the pci cap and pcie ext cap.
Tested on x86 and powerpc.
Wei Yang (3):
PCI: move PCI_FIND_CAP_TTL to pci.h and use it in quirks
PCI: use u8 instead of int for pci configuration space pos and cap
PCI: use u16 instead of int for pci express extended capabilities pos
and cap
drivers/pci/iov.c | 2 +-
drivers/pci/pci.c | 68 +++++++++++++++++++++++++-------------------------
drivers/pci/probe.c | 10 ++++----
drivers/pci/quirks.c | 19 +++++++-------
include/linux/pci.h | 28 +++++++++++----------
5 files changed, 65 insertions(+), 62 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-10-14 6:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 6:47 Wei Yang [this message]
2014-10-14 6:47 ` [PATCH 1/3] PCI: move PCI_FIND_CAP_TTL to pci.h and use it in quirks Wei Yang
2014-10-22 23:18 ` Bjorn Helgaas
2014-10-24 3:44 ` Wei Yang
2014-11-06 3:12 ` Wei Yang
2014-11-18 9:16 ` Wei Yang
2014-10-14 6:47 ` [PATCH 2/3] PCI: use u8 instead of int for pci configuration space pos and cap Wei Yang
2014-10-22 23:23 ` Bjorn Helgaas
2014-10-24 3:49 ` Wei Yang
2014-10-14 6:47 ` [PATCH 3/3] PCI: use u16 instead of int for pci express extended capabilities " Wei Yang
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=1413269253-8990-1-git-send-email-weiyang@linux.vnet.ibm.com \
--to=weiyang@linux.vnet.ibm.com \
--cc=bhelgaas@google.com \
--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).