From: Toshi Kani <toshi.kani@hp.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
linux-acpi@vger.kernel.org, lenb@kernel.org,
linux-kernel@vger.kernel.org, liuj97@gmail.com
Subject: Re: [PATCH 2/2] ACPI: Remove unused lockable in acpi_device_flags
Date: Thu, 25 Oct 2012 08:01:54 -0600 [thread overview]
Message-ID: <1351173714.19172.27.camel@misato.fc.hp.com> (raw)
In-Reply-To: <4977274.iWiO0dh4FZ@vostro.rjw.lan>
On Thu, 2012-10-25 at 00:08 +0200, Rafael J. Wysocki wrote:
> On Wednesday 17 of October 2012 07:56:49 Toshi Kani wrote:
> > On Wed, 2012-10-17 at 10:26 +0900, Yasuaki Ishimatsu wrote:
> > > 2012/10/16 1:34, Toshi Kani wrote:
> > > > Removed lockable in struct acpi_device_flags since it is no
> > > > longer used by any code. acpi_bus_hot_remove_device() cannot
> > > > use this flag because acpi_bus_trim() frees up its acpi_device
> > > > object. Furthermore, the dock driver calls _LCK method without
> > > > using this lockable flag.
> > > >
> > > > Signed-off-by: Toshi Kani <toshi.kani@hp.com>
> > >
> > > Looks good to me.
> > > Reviewed-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
> >
> > Thanks Yasuaki for reviewing!
>
> Applied to linux-pm.git/acpi-next as v3.8 material.
Cool! Thanks Rafael!
-Toshi
> Thanks,
> Rafael
next prev parent reply other threads:[~2012-10-25 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 16:34 [PATCH 1/2] ACPI: Fix stale pointer access to flags.lockable Toshi Kani
2012-10-15 16:34 ` [PATCH 2/2] ACPI: Remove unused lockable in acpi_device_flags Toshi Kani
2012-10-17 1:26 ` Yasuaki Ishimatsu
2012-10-17 1:26 ` Yasuaki Ishimatsu
2012-10-17 13:56 ` Toshi Kani
2012-10-24 22:08 ` Rafael J. Wysocki
2012-10-25 14:01 ` Toshi Kani [this message]
2012-10-17 1:25 ` [PATCH 1/2] ACPI: Fix stale pointer access to flags.lockable Yasuaki Ishimatsu
2012-10-17 1:25 ` Yasuaki Ishimatsu
2012-10-17 13:55 ` Toshi Kani
2012-10-24 22:08 ` 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=1351173714.19172.27.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=rjw@sisk.pl \
/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.