[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75Vd+kqgwiJxGbGg3abFgez6Af8j5Qnr0-VAWtayx+vTmYg@mail.gmail.com>
Date: Wed, 7 Jun 2017 19:55:15 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: joeyli <jlee@...e.com>
Cc: "Lee, Chun-Yi" <joeyli.kernel@...il.com>,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Len Brown <lenb@...nel.org>
Subject: Re: [PATCH] acpi: handle the acpi hotplug schedule error
On Wed, Jun 7, 2017 at 6:39 PM, joeyli <jlee@...e.com> wrote:
> On Wed, Jun 07, 2017 at 01:46:37PM +0300, Andy Shevchenko wrote:
>> On Wed, Jun 7, 2017 at 1:18 PM, joeyli <jlee@...e.com> wrote:
>> > On Wed, Jun 07, 2017 at 11:36:55AM +0300, Andy Shevchenko wrote:
>> >> On Wed, Jun 7, 2017 at 9:05 AM, Lee, Chun-Yi <joeyli.kernel@...il.com> wrote:
> I think normally it should be success. So how about:
>
> if (hotplug_event) {
> if (ACPI_SUCCESS(acpi_hotplug_schedule(adev, type)))
> return;
> goto err_put_device;
> }
Fine by me.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists