public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn@helgaas.com>
To: Thomas Renninger <trenn@suse.de>
Cc: lenb@kernel.org, robert.moore@intel.com, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] pnpacpi: Better format error message
Date: Tue, 1 Mar 2011 09:25:04 -0700	[thread overview]
Message-ID: <20110301162504.GC2940@helgaas.com> (raw)
In-Reply-To: <201103011524.50340.trenn@suse.de>

On Tue, Mar 01, 2011 at 03:24:50PM +0100, Thomas Renninger wrote:
> On a system with empty _CRS method I see:
> pnp 00:0c: can't evaluate _CRS: 12311
> which is 0x3017, which would mean: AE_AML_INVALID_RESOURCE_TYPE
> 
> This patch would directly show: AE_AML_INVALID_RESOURCE_TYPE

The patch seems fine to me, but I question whether we need these
printks at all.  It seems pointless to have an empty _CRS method,
but it does seem legal, or at least debatable, so I'm not sure
that the message is telling us anything useful.

Bjorn

> Signed-off-by: Thomas Renninger <trenn@suse.de>
> CC: bjorn@helgaas.com
> CC: lenb@kernel.org
> CC: robert.moore@intel.com
> 
> ---
> Corrected email address of Bjorn.
> 
>  drivers/pnp/pnpacpi/rsparser.c |   12 ++++++++----
>  1 file changed, 8 insertions(+), 4 deletions(-)
> 
> Index: linux-2.6.37-master/drivers/pnp/pnpacpi/rsparser.c
> ===================================================================
> --- linux-2.6.37-master.orig/drivers/pnp/pnpacpi/rsparser.c
> +++ linux-2.6.37-master/drivers/pnp/pnpacpi/rsparser.c
> @@ -498,7 +498,8 @@ int pnpacpi_parse_allocated_resource(str
>  
>  	if (ACPI_FAILURE(status)) {
>  		if (status != AE_NOT_FOUND)
> -			dev_err(&dev->dev, "can't evaluate _CRS: %d", status);
> +			dev_err(&dev->dev, "can't evaluate _CRS: %s",
> +				acpi_format_exception(status));
>  		return -EPERM;
>  	}
>  	return 0;
> @@ -809,7 +810,8 @@ int __init pnpacpi_parse_resource_option
>  
>  	if (ACPI_FAILURE(status)) {
>  		if (status != AE_NOT_FOUND)
> -			dev_err(&dev->dev, "can't evaluate _PRS: %d", status);
> +			dev_err(&dev->dev, "can't evaluate _PRS: %s",
> +				acpi_format_exception(status));
>  		return -EPERM;
>  	}
>  	return 0;
> @@ -876,7 +878,8 @@ int pnpacpi_build_resource_template(stru
>  	status = acpi_walk_resources(handle, METHOD_NAME__CRS,
>  				     pnpacpi_count_resources, &res_cnt);
>  	if (ACPI_FAILURE(status)) {
> -		dev_err(&dev->dev, "can't evaluate _CRS: %d\n", status);
> +		dev_err(&dev->dev, "can't evaluate _CRS: %s\n",
> +			acpi_format_exception(status));
>  		return -EINVAL;
>  	}
>  	if (!res_cnt)
> @@ -891,7 +894,8 @@ int pnpacpi_build_resource_template(stru
>  				     pnpacpi_type_resources, &resource);
>  	if (ACPI_FAILURE(status)) {
>  		kfree(buffer->pointer);
> -		dev_err(&dev->dev, "can't evaluate _CRS: %d\n", status);
> +		dev_err(&dev->dev, "can't evaluate _CRS: %s\n",
> +			acpi_format_exception(status));
>  		return -EINVAL;
>  	}
>  	/* resource will pointer the end resource now */

       reply	other threads:[~2011-03-01 16:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201103011513.40235.trenn@suse.de>
     [not found] ` <201103011524.50340.trenn@suse.de>
2011-03-01 16:25   ` Bjorn Helgaas [this message]
     [not found]     ` <201103011743.33975.trenn@suse.de>
2011-03-01 17:03       ` [PATCH] pnpacpi: Better format error message Moore, Robert
2011-03-01 21:08         ` Thomas Renninger
2011-03-01 22:25           ` Moore, Robert

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=20110301162504.GC2940@helgaas.com \
    --to=bjorn@helgaas.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=robert.moore@intel.com \
    --cc=trenn@suse.de \
    /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