From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
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: Tue, 16 Jul 2013 13:51:58 +0200 [thread overview]
Message-ID: <1395450.yBeZCSijNz@vostro.rjw.lan> (raw)
In-Reply-To: <20130716053641.GU4898@intel.com>
On Tuesday, July 16, 2013 08:36:41 AM Mika Westerberg wrote:
> On Tue, Jul 16, 2013 at 02:31:15AM +0200, Rafael J. Wysocki wrote:
> > On Sunday, July 14, 2013 10:08:28 AM Mika Westerberg wrote:
> > > 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.
> >
> > Can you please apply the appended patch on top of the current
> > linux-pm.git/bleeding-edge and check if things still work then on the test
> > systems?
>
> Tested on both systems with the patch applied and Thunderbolt still works
> fine.
Thanks for the confirmation!
I'm going to fold this code into the "ACPI / hotplug / PCI: Check for new devices
on enabled slots" patch and resend the whole series without the "RFC" mark.
I'll add your "Tested-by" to it if you don't mind.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-07-16 11:42 UTC|newest]
Thread overview: 7+ 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
2013-07-14 15:12 ` Rafael J. Wysocki
2013-07-16 0:31 ` Rafael J. Wysocki
2013-07-16 5:36 ` Mika Westerberg
2013-07-16 11:51 ` Rafael J. Wysocki [this message]
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=1395450.yBeZCSijNz@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--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