linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI / resources: Use AE_CTRL_TERMINATE to terminate resources walks
Date: Fri, 16 Nov 2012 16:27:58 +0200	[thread overview]
Message-ID: <20121116142758.GU17774@intel.com> (raw)
In-Reply-To: <1453537.D7nc72D9LF@vostro.rjw.lan>

On Fri, Nov 16, 2012 at 02:49:10PM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> 
> Currently acpi_dev_process_resource() returns AE_ABORT_METHOD
> to terminate the acpi_walk_resources() it is called from if
> the .preproc() routine provided by the caller of
> acpi_dev_get_resources() initiating the resources walk returns
> an error code.  It is better to use AE_CTRL_TERMINATE for this
> purpose, however, so do that.
> 
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>

> ---
>  drivers/acpi/resource.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Index: linux/drivers/acpi/resource.c
> ===================================================================
> --- linux.orig/drivers/acpi/resource.c
> +++ linux/drivers/acpi/resource.c
> @@ -446,7 +446,7 @@ static acpi_status acpi_dev_process_reso
>  		ret = c->preproc(ares, c->preproc_data);
>  		if (ret < 0) {
>  			c->error = ret;
> -			return AE_ABORT_METHOD;
> +			return AE_CTRL_TERMINATE;
>  		} else if (ret > 0) {
>  			return AE_OK;
>  		}

      reply	other threads:[~2012-11-16 14:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 13:49 [PATCH] ACPI / resources: Use AE_CTRL_TERMINATE to terminate resources walks Rafael J. Wysocki
2012-11-16 14:27 ` Mika Westerberg [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=20121116142758.GU17774@intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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).