mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Scally <djrscally@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	lenb@kernel.org, mika.westerberg@linux.intel.com
Subject: Re: [PATCH] acpi: resource: Use AE_ABORT_METHOD to terminate acpi_dev_get_resources()
Date: Sat, 5 Dec 2020 16:59:14 +0000	[thread overview]
Message-ID: <884a73ea-0bc3-6598-b440-3d7c6a8561b6@gmail.com> (raw)
In-Reply-To: <2246133.BJYN6MDhT9@kreacher>

On 05/12/2020 15:21, Rafael J. Wysocki wrote:
> On Friday, December 4, 2020 1:27:40 AM CET Daniel Scally wrote:
>> Switching this function to AE_CTRL_TERMINATE broke the documented
>> behaviour of acpi_dev_get_resources() - AE_CTRL_TERMINATE does not, in
>> fact, terminate the resource walk because acpi_walk_resource_buffer()
>> ignores it (specifically converting it to AE_OK), referring to that
>> value as "an OK termination by the user function". This means that
>> acpi_dev_get_resources() does not abort processing when the preproc
>> function returns a negative value.
>>
>> Revert to AE_ABORT_METHOD
>>
>> Fixes: 8a66790b7850 ("ACPI / resources: Use AE_CTRL_TERMINATE to terminate resources walks")
>> Signed-off-by: Daniel Scally <djrscally@gmail.com>
> This is simply a revert of the above commit, so it would be better to present
> it as a revert explicitly.

Ah, of course. I'll resend as that, sorry for the noise

>
>> ---
>>  drivers/acpi/resource.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/acpi/resource.c b/drivers/acpi/resource.c
>> index ad04824ca3ba..f2f5f1dc7c61 100644
>> --- a/drivers/acpi/resource.c
>> +++ b/drivers/acpi/resource.c
>> @@ -541,7 +541,7 @@ static acpi_status acpi_dev_process_resource(struct acpi_resource *ares,
>>  		ret = c->preproc(ares, c->preproc_data);
>>  		if (ret < 0) {
>>  			c->error = ret;
>> -			return AE_CTRL_TERMINATE;
>> +			return AE_ABORT_METHOD;
>>  		} else if (ret > 0) {
>>  			return AE_OK;
>>  		}
>>
>
>
>

      reply	other threads:[~2020-12-05 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04  0:27 Daniel Scally
2020-12-05 15:21 ` Rafael J. Wysocki
2020-12-05 16:59   ` Dan Scally [this message]

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=884a73ea-0bc3-6598-b440-3d7c6a8561b6@gmail.com \
    --to=djrscally@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --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

all inboxes | Powered by JetHome®