[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1752714.boAZzg4FTs@vostro.rjw.lan>
Date: Thu, 18 Jul 2013 20:59:25 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Yinghai Lu <yinghai@...nel.org>
Cc: ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux PCI <linux-pci@...r.kernel.org>,
Jiang Liu <liuj97@...il.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
Subject: Re: [PATCH 5/30] ACPI / hotplug / PCI: Unified notify handler for hotplug events
On Wednesday, July 17, 2013 07:07:02 PM Yinghai Lu wrote:
> On Wed, Jul 17, 2013 at 4:18 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > From: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
> >
> > Using the hotplug context objects introduced previously rework the
> > ACPI-based PCI hotplug (ACPIPHP) core code so that all notifications
> > for ACPI device objects corresponding to the hotplug PCI devices are
> > handled by one function, handle_hotplug_event(), which recognizes
> > whether it has to handle a bridge or a function.
> >
> > In addition to code size reduction it allows some ugly pieces of code
> > where notify handlers have to be uninstalled and installed again to
> > go away. Moreover, it fixes a theoretically possible race between
> > handle_hotplug_event() and free_bridge() tearing down data structures
> > for the same handle.
> >
> > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
> > ---
> > drivers/pci/hotplug/acpiphp.h | 1
> > drivers/pci/hotplug/acpiphp_glue.c | 132 ++++++++++++++-----------------------
> > 2 files changed, 53 insertions(+), 80 deletions(-)
>
> Can you put this patches in one temp branch ?
They are in linux-pm.git/bleeding-edge.
>
> Like to check final bits.
Sure.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists