From: Greg KH <gregkh@linuxfoundation.org>
To: Bill Pemberton <wfp5p@virginia.edu>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 0/9] PCI: Remove use of CONFIG_HOTPLUG
Date: Wed, 28 Nov 2012 11:01:06 -0800 [thread overview]
Message-ID: <20121128190106.GA30376@kroah.com> (raw)
In-Reply-To: <1353530100-728-1-git-send-email-wfp5p@virginia.edu>
On Wed, Nov 21, 2012 at 03:34:51PM -0500, Bill Pemberton wrote:
> This is a respin of the patches to remove CONFIG_HOTPLUG for the PCI
> subsystem. The end result is the same as the patches in the big
> patchset I sent out earlier this week but the changelog entries have
> been changed to be consistent with the capitalization of PCI. The
> removal of the __dev* entries has also been squashed into a single
> patch.
Bjorn, any objection for me taking these patches through my driver-core
tree? If not, can I get your ack?
thanks,
greg k-h
next prev parent reply other threads:[~2012-11-28 19:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 20:34 [PATCH 0/9] PCI: Remove use of CONFIG_HOTPLUG Bill Pemberton
2012-11-21 20:34 ` [PATCH 1/9] microblaze/PCI: Remove CONFIG_HOTPLUG ifdefs Bill Pemberton
2012-11-21 20:34 ` [PATCH 2/9] mips/PCI: " Bill Pemberton
2012-11-21 20:34 ` [PATCH 3/9] powerpc/PCI: " Bill Pemberton
2012-11-21 20:34 ` [PATCH 4/9] sh/PCI: " Bill Pemberton
2012-11-21 20:34 ` [PATCH 5/9] unicore32/PCI: " Bill Pemberton
2012-11-29 2:02 ` guanxuetao
2012-11-21 20:34 ` [PATCH 6/9] PCI: " Bill Pemberton
2012-11-21 20:34 ` [PATCH 7/9] PCI: Move pci_uevent into pci-driver.c Bill Pemberton
2012-11-21 20:34 ` [PATCH 8/9] PCI: Always build setup-bus when PCI is enabled Bill Pemberton
2012-11-21 20:35 ` [PATCH 9/9] PCI: Remove __dev* markings Bill Pemberton
2012-11-28 19:01 ` Greg KH [this message]
2012-11-28 20:04 ` [PATCH 0/9] PCI: Remove use of CONFIG_HOTPLUG 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=20121128190106.GA30376@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=wfp5p@virginia.edu \
/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