From: Bjorn Helgaas <bhelgaas@google.com>
To: linux-pci@vger.kernel.org
Cc: Lee Jones <lee.jones@linaro.org>, Samuel Ortiz <sameo@linux.intel.com>
Subject: [PATCH 0/5] PCIe capability #define tidyup
Date: Tue, 27 Aug 2013 13:00:17 -0600 [thread overview]
Message-ID: <20130827185731.16595.52864.stgit@bhelgaas-glaptop> (raw)
These clean up some PCIe capability #defines and comments.
The first renames a few #defines that are used in drivers/mfd/rts5227.c.
The rest are whitespace and comment changes that should have no effect on
any users.
I propose to put these in v3.12 unless there are issues.
---
Bjorn Helgaas (5):
PCI: Rename PCIe capability definitions to follow convention
PCI: Clarify PCI_EXP_TYPE_PCI_BRIDGE comment
PCI: Remove obsolete comment reference to pci_pcie_cap2()
PCI: Tidy bitmasks and spacing of PCIe capability definitions
PCI: Add offsets of PCIe capability registers
drivers/mfd/rts5227.c | 2 -
drivers/pci/pci.c | 31 ++++++-----
include/uapi/linux/pci_regs.h | 113 +++++++++++++++++++++--------------------
3 files changed, 77 insertions(+), 69 deletions(-)
next reply other threads:[~2013-08-27 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 19:00 Bjorn Helgaas [this message]
2013-08-27 19:00 ` [PATCH 1/5] PCI: Rename PCIe capability definitions to follow convention Bjorn Helgaas
2013-08-27 22:05 ` Samuel Ortiz
2013-08-27 19:00 ` [PATCH 2/5] PCI: Clarify PCI_EXP_TYPE_PCI_BRIDGE comment Bjorn Helgaas
2013-08-27 19:00 ` [PATCH 3/5] PCI: Remove obsolete comment reference to pci_pcie_cap2() Bjorn Helgaas
2013-08-27 19:00 ` [PATCH 4/5] PCI: Tidy bitmasks and spacing of PCIe capability definitions Bjorn Helgaas
2013-08-27 19:00 ` [PATCH 5/5] PCI: Add offsets of PCIe capability registers Bjorn Helgaas
2013-08-29 3:15 ` [PATCH 0/5] PCIe capability #define tidyup Bjorn Helgaas
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=20130827185731.16595.52864.stgit@bhelgaas-glaptop \
--to=bhelgaas@google.com \
--cc=lee.jones@linaro.org \
--cc=linux-pci@vger.kernel.org \
--cc=sameo@linux.intel.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