From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: [git pull] more 2.6.27 PCI bits
Date: Thu, 24 Jul 2008 13:50:48 -0700 [thread overview]
Message-ID: <200807241350.48482.jbarnes@virtuousgeek.org> (raw)
Please pull my for-linus branch:
git pull git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6.git for-linus
It doesn't contain anything particularly exciting since it looks like we'll
have to wait until 2.6.28 for the resource allocation improvements.
Shortlog & diffstat below.
Thanks,
Jesse
Alex Chiang (1):
PCI hotplug: fix error path in pci_slot's register_slot
Harvey Harrison (1):
PCI: fixup sparse endianness warnings in proc.c
Rafael J. Wysocki (1):
PCI PM: make more PCI PM core functionality available to drivers
Yong Wang (1):
PCI/DMAR: don't assume presence of RMRRs
drivers/acpi/pci_slot.c | 5 +++--
drivers/pci/dmar.c | 4 +---
drivers/pci/pci.c | 34 ++++++++++++++++++++++++----------
drivers/pci/proc.c | 18 +++++++++---------
include/linux/pci.h | 2 ++
5 files changed, 39 insertions(+), 24 deletions(-)
reply other threads:[~2008-07-24 20:51 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=200807241350.48482.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=torvalds@linux-foundation.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