From: Toshi Kani <toshi.kani@hp.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI / hotplug: Rework deferred execution of acpi_device_hotplug()
Date: Tue, 04 Mar 2014 12:53:05 -0700 [thread overview]
Message-ID: <1393962785.6784.110.camel@misato.fc.hp.com> (raw)
In-Reply-To: <1573287.V189PcUPxA@vostro.rjw.lan>
On Sat, 2014-03-01 at 20:57 +0000, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Since the only function executed by acpi_hotplug_execute() is
> acpi_device_hotplug() and it only is called by the ACPI core,
> simplify its definition so that it only takes two arguments, the
> ACPI device object pointer and event code, rename it to
> acpi_hotplug_schedule() and move its header from acpi_bus.h to
> the ACPI core's internal header file internal.h. Modify the
> definition of acpi_device_hotplug() so that its first argument is
> an ACPI device object pointer and modify the definition of
> struct acpi_hp_work accordingly.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
The change looks good to me. I wonder if acpi_hotplug_schedule() should
still be in acpi/osl.c after this change, though.
Acked-by: Toshi Kani <toshi.kani@hp.com>
Thanks,
-Toshi
next prev parent reply other threads:[~2014-03-04 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 20:57 [PATCH] ACPI / hotplug: Rework deferred execution of acpi_device_hotplug() Rafael J. Wysocki
2014-03-04 19:53 ` Toshi Kani [this message]
2014-03-05 0:34 ` 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=1393962785.6784.110.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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