From: Yinghai Lu <yinghai@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH 0/5] PCI: hotplug related misc patches
Date: Tue, 10 Jul 2012 12:30:47 -0700 [thread overview]
Message-ID: <CAE9FiQXK=ByAkjVU53ftMYchsGSKD-yCLUpCLNZoZA_7=bzWOw@mail.gmail.com> (raw)
In-Reply-To: <1340437325-29282-1-git-send-email-yinghai@kernel.org>
On Sat, Jun 23, 2012 at 12:42 AM, Yinghai Lu <yinghai@kernel.org> wrote:
> minor changes that should be safe for 3.6
>
> could get from
> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci-next
>
> Yinghai Lu (5):
> PCI, acpiphp: remove not used res_lock
> pciehp: Don't enable presence notification while surprise removal is
> not supported.
> PCI, acpiphp: Merge acpiphp_debug and debug
> PCI, acpiphp: add is_hotplug_bridge detection
> PCI: add root bus children dev's res to fail list
>
> drivers/pci/hotplug/acpiphp.h | 4 +---
> drivers/pci/hotplug/acpiphp_core.c | 7 ++-----
> drivers/pci/hotplug/acpiphp_glue.c | 30 ++++++++++++++++++++++++++----
> drivers/pci/hotplug/pciehp_hpc.c | 5 +++--
> drivers/pci/setup-bus.c | 2 +-
> 5 files changed, 33 insertions(+), 15 deletions(-)
can you put those 5 patches into pci/next?
Those should be safe for v3.6 merging window.
Thanks
Yinghai
next prev parent reply other threads:[~2012-07-10 19:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 7:42 [PATCH 0/5] PCI: hotplug related misc patches Yinghai Lu
2012-06-23 7:42 ` [PATCH 1/5] PCI, acpiphp: remove not used res_lock Yinghai Lu
2012-06-23 7:42 ` [PATCH 2/5] pciehp: Don't enable presence notification while surprise removal is not supported Yinghai Lu
2012-06-26 1:26 ` Kaneshige, Kenji
2012-06-26 18:03 ` Yinghai Lu
2012-07-10 22:56 ` Bjorn Helgaas
2012-07-10 23:12 ` Yinghai Lu
2012-07-10 23:28 ` Bjorn Helgaas
2012-07-10 23:40 ` Yinghai Lu
2012-07-11 16:21 ` Bjorn Helgaas
2012-07-11 17:58 ` Yinghai Lu
2012-07-11 18:15 ` Bjorn Helgaas
2012-07-11 18:49 ` Yinghai Lu
2012-07-11 19:56 ` Bjorn Helgaas
2012-07-11 20:28 ` Yinghai Lu
2012-07-11 20:48 ` Bjorn Helgaas
2012-07-11 20:56 ` Yinghai Lu
2012-07-11 22:24 ` Bjorn Helgaas
2012-07-12 0:05 ` Yinghai Lu
2012-07-12 20:20 ` Bjorn Helgaas
2012-07-13 0:19 ` Yinghai Lu
2012-07-13 15:30 ` Bjorn Helgaas
2012-07-13 18:07 ` Yinghai Lu
2012-06-23 7:42 ` [PATCH 3/5] PCI, acpiphp: Merge acpiphp_debug and debug Yinghai Lu
2012-06-23 7:42 ` [PATCH 4/5] PCI, acpiphp: add is_hotplug_bridge detection Yinghai Lu
2012-07-11 15:50 ` Bjorn Helgaas
2012-07-11 17:14 ` Jason Baron
2012-07-11 19:42 ` Bjorn Helgaas
2012-07-16 16:05 ` Bjorn Helgaas
2012-07-17 14:14 ` Jason Baron
2012-08-15 19:36 ` Bjorn Helgaas
2012-08-20 14:35 ` Jason Baron
2012-08-22 23:19 ` Bjorn Helgaas
2012-09-04 20:55 ` Jason Baron
2012-06-23 7:42 ` [PATCH 5/5] PCI: add root bus children dev's res to fail list Yinghai Lu
2012-07-10 19:30 ` Yinghai Lu [this message]
2012-07-11 18:32 ` [PATCH 0/5] PCI: hotplug related misc patches 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='CAE9FiQXK=ByAkjVU53ftMYchsGSKD-yCLUpCLNZoZA_7=bzWOw@mail.gmail.com' \
--to=yinghai@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.