From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-acpi@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Yinghai Lu <yinghai@kernel.org>, Jiang Liu <liuj97@gmail.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH] PCI / hotplug / ACPI: Get rid of check_sub_bridges()
Date: Sun, 14 Jul 2013 10:08:28 +0300 [thread overview]
Message-ID: <20130714070828.GS4898@intel.com> (raw)
In-Reply-To: <3395919.UaDiFX78Zn@vostro.rjw.lan>
On Sat, Jul 13, 2013 at 11:47:26PM +0200, Rafael J. Wysocki wrote:
> On Saturday, July 13, 2013 08:09:59 PM Mika Westerberg wrote:
> > Now that acpiphp_check_bridge() always enumerates devices behind the
> > bridge, there is no need to do that for each sub-bridge anymore like it is
> > done in the current ACPI-based PCI hotplug code. Given this we don't need
> > check_sub_bridges() anymore and can drop the function completely.
> >
> > This also simplifies the ACPIPHP code a bit.
> >
> > Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> > ---
> > This applies on top of v3.10 with Rafael's ACPIPHP + Thunderbolt series
> > applied:
> >
>
> OK, I added it to my bleeding-edge branch along with this series:
>
> > http://www.spinics.net/lists/linux-acpi/msg44480.html
>
> rebased on top of some previous ACPI cleanup commits. I needed to make some
> changes in the process (and fixed up some breakage reported by the auto build
> testing), hopefully I didn't break anything. If you're in an adventurous mood,
> testing would be welcome. ;-) [That already includes the majority of 3.11
> material from Linus, though, so unexpected breakage elsewhere may happen.]
Tried the bleeding-edge branch on both of our test machines and Thunderbolt
still works fine.
next prev parent reply other threads:[~2013-07-14 7:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-13 17:09 [PATCH] PCI / hotplug / ACPI: Get rid of check_sub_bridges() Mika Westerberg
2013-07-13 21:47 ` Rafael J. Wysocki
2013-07-14 7:08 ` Mika Westerberg [this message]
2013-07-14 15:12 ` Rafael J. Wysocki
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=20130714070828.GS4898@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@sisk.pl \
--cc=yinghai@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