linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: joeyli <jlee@suse.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Len Brown <lenb@kernel.org>, Michal Hocko <mhocko@suse.cz>
Subject: Re: [PATCH v2] acpi: handle the acpi hotplug schedule error
Date: Fri, 30 Jun 2017 07:16:49 +0800	[thread overview]
Message-ID: <20170629231649.GA13714@linux-l9pv.suse> (raw)
In-Reply-To: <2576656.sje5KLSpq7@aspire.rjw.lan>

Hi Rafael, 

Thanks for your review.

On Thu, Jun 29, 2017 at 12:06:20AM +0200, Rafael J. Wysocki wrote:
> On Wednesday, June 21, 2017 03:04:34 PM Lee, Chun-Yi wrote:
> > Kernel should decrements the reference count of acpi device
> > when the scheduling of acpi hotplug work is failed, and
> > evaluates _OST to notify BIOS the failure.
> > 
> > v2:
> > To simplify the code. (Andy Shevchenko)
> > 
> > Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> > Cc: Len Brown <lenb@kernel.org>
> > Cc: Michal Hocko <mhocko@suse.cz>
> > Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> > Signed-off-by: "Lee, Chun-Yi" <jlee@suse.com>
> 
> Well, what about:
> 
>     if (!hotplug_event) {
>         acpi_bus_put_acpi_device(adev);
>         return;
>     }
> 
>     if (ACPI_SUCCESS(acpi_hotplug_schedule(adev, type)))
>         return;
> 
>     acpi_bus_put_acpi_device(adev);
> 
> err:
>     acpi_evaluate_ost(handle, type, ost_code, NULL);
> 
> This achieves the same as the patch below to my eyes, but looks
> less convoluted IMO.
> 

Yes, that's better. I will send v3 patch.

Joey Lee

> 
> > ---
> >  drivers/acpi/bus.c | 9 +++++++--
> >  1 file changed, 7 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
> > index 34fbe02..91adb71 100644
> > --- a/drivers/acpi/bus.c
> > +++ b/drivers/acpi/bus.c
> > @@ -427,12 +427,17 @@ static void acpi_bus_notify(acpi_handle handle, u32 type, void *data)
> >  	    (driver->flags & ACPI_DRIVER_ALL_NOTIFY_EVENTS))
> >  		driver->ops.notify(adev, type);
> >  
> > -	if (hotplug_event && ACPI_SUCCESS(acpi_hotplug_schedule(adev, type)))
> > -		return;
> > +	if (hotplug_event) {
> > +		if (ACPI_SUCCESS(acpi_hotplug_schedule(adev, type)))
> > +			return;
> > +		goto err_put_device;
> > +	}
> >  
> >  	acpi_bus_put_acpi_device(adev);
> >  	return;
> >  
> > + err_put_device:
> > +	acpi_bus_put_acpi_device(adev);
> >   err:
> >  	acpi_evaluate_ost(handle, type, ost_code, NULL);
> >  }
> > 
> 

  reply	other threads:[~2017-06-29 23:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21  7:04 [PATCH v2] acpi: handle the acpi hotplug schedule error Lee, Chun-Yi
2017-06-28 22:06 ` Rafael J. Wysocki
2017-06-29 23:16   ` joeyli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-06-13 11:11 Lee, Chun-Yi
2017-06-09  4:33 Lee, Chun-Yi
2017-06-09  9:40 ` Andy Shevchenko

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=20170629231649.GA13714@linux-l9pv.suse \
    --to=jlee@suse.com \
    --cc=joeyli.kernel@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).