All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	lenb@kernel.org, wency@cn.fujitsu.com,
	vasilis.liaskovitis@profitbricks.com
Subject: Re: acpi : acpi_bus_trim() stops removing devices when failing to remove the device
Date: Thu, 11 Oct 2012 14:40:34 +0900	[thread overview]
Message-ID: <50765BD2.10705@jp.fujitsu.com> (raw)
In-Reply-To: <1349874065.23493.23.camel@misato.fc.hp.com>

Hi Toshi,

2012/10/10 22:01, Toshi Kani wrote:
> On Wed, 2012-10-10 at 10:07 +0900, Yasuaki Ishimatsu wrote:
>   :
>>>>    	if (acpi_drv) {
>>>>    		if (acpi_drv->ops.notify)
>>>>    			acpi_device_remove_notify_handler(acpi_dev);
>
> THIS CALL
>
>>>> -		if (acpi_drv->ops.remove)
>>>> -			acpi_drv->ops.remove(acpi_dev, acpi_dev->removal_type);
>>>> +		if (acpi_drv->ops.remove) {
>>>> +			ret = acpi_drv->ops.remove(acpi_dev,
>>>> +						   acpi_dev->removal_type);
>>>> +			if (ret)
>>>
>>> Hi Yasuaki,
>>>
>>> Shouldn't the notify handler be reinstalled here if it was removed by
>>> the acpi_device_remove_notify_handler() above?
>>
>> I do not reinstall the notify handler.
>> The function has not been removed on linux-3.6. And the patch is created
>> on linux-3.6. So the function remains in the patch.
>
> Umm... I am not sure what you meant.  Let me clarify my comment.  When
> acpi_drv->ops.remove() failed, I thought we would need to roll-back the
> procedure done by the acpi_device_remove_notify_handler() call, which I
> indicated as "THIS CALL" above.  So, in this error path, don't we need
> something like below?
>
> if (acpi_drv->ops.notify)
> 	acpi_device_install_notify_handler(acpi_dev)

I understood what you said.  I'll update it.

Thanks,
Yasuaki Ishimatsu

>
> Thanks,
> -Toshi
>
>
>
>



WARNING: multiple messages have this Message-ID (diff)
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<lenb@kernel.org>, <wency@cn.fujitsu.com>,
	<vasilis.liaskovitis@profitbricks.com>
Subject: Re: acpi : acpi_bus_trim() stops removing devices when failing to remove the device
Date: Thu, 11 Oct 2012 14:40:34 +0900	[thread overview]
Message-ID: <50765BD2.10705@jp.fujitsu.com> (raw)
In-Reply-To: <1349874065.23493.23.camel@misato.fc.hp.com>

Hi Toshi,

2012/10/10 22:01, Toshi Kani wrote:
> On Wed, 2012-10-10 at 10:07 +0900, Yasuaki Ishimatsu wrote:
>   :
>>>>    	if (acpi_drv) {
>>>>    		if (acpi_drv->ops.notify)
>>>>    			acpi_device_remove_notify_handler(acpi_dev);
>
> THIS CALL
>
>>>> -		if (acpi_drv->ops.remove)
>>>> -			acpi_drv->ops.remove(acpi_dev, acpi_dev->removal_type);
>>>> +		if (acpi_drv->ops.remove) {
>>>> +			ret = acpi_drv->ops.remove(acpi_dev,
>>>> +						   acpi_dev->removal_type);
>>>> +			if (ret)
>>>
>>> Hi Yasuaki,
>>>
>>> Shouldn't the notify handler be reinstalled here if it was removed by
>>> the acpi_device_remove_notify_handler() above?
>>
>> I do not reinstall the notify handler.
>> The function has not been removed on linux-3.6. And the patch is created
>> on linux-3.6. So the function remains in the patch.
>
> Umm... I am not sure what you meant.  Let me clarify my comment.  When
> acpi_drv->ops.remove() failed, I thought we would need to roll-back the
> procedure done by the acpi_device_remove_notify_handler() call, which I
> indicated as "THIS CALL" above.  So, in this error path, don't we need
> something like below?
>
> if (acpi_drv->ops.notify)
> 	acpi_device_install_notify_handler(acpi_dev)

I understood what you said.  I'll update it.

Thanks,
Yasuaki Ishimatsu

>
> Thanks,
> -Toshi
>
>
>
>



  reply	other threads:[~2012-10-11  5:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09  8:48 acpi : acpi_bus_trim() stops removing devices when failing to remove the device Yasuaki Ishimatsu
2012-10-09  8:48 ` Yasuaki Ishimatsu
2012-10-09 16:36 ` Toshi Kani
2012-10-10  1:07   ` Yasuaki Ishimatsu
2012-10-10  1:07     ` Yasuaki Ishimatsu
2012-10-10 13:01     ` Toshi Kani
2012-10-11  5:40       ` Yasuaki Ishimatsu [this message]
2012-10-11  5:40         ` Yasuaki Ishimatsu

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=50765BD2.10705@jp.fujitsu.com \
    --to=isimatu.yasuaki@jp.fujitsu.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toshi.kani@hp.com \
    --cc=vasilis.liaskovitis@profitbricks.com \
    --cc=wency@cn.fujitsu.com \
    /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.