From: Thomas Renninger <trenn@suse.de>
To: Holger Macht <hmacht@suse.de>
Cc: linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>,
Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Subject: Re: [PATCH] ACPI: Do not pass NULL to acpi_get_handle() when looking for _EJD
Date: Thu, 14 Feb 2008 15:49:40 +0100 [thread overview]
Message-ID: <1203000580.7977.703.camel@queen.suse.de> (raw)
In-Reply-To: <20080214124034.GA9708@homac.suse.de>
On Thu, 2008-02-14 at 13:40 +0100, Holger Macht wrote:
> When trying to get the acpi_handle from an acpi_buffer, pass
> ACPI_ROOT_OBJECT instead of NULL to acpi_get_handle(). This fixes the
> detection of dock dependent bays.
>
>
> Signed-off-by: Holger Macht <hmacht@suse.de>
> ---
>
> diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
> index 3fac011..d9b9143 100644
> --- a/drivers/acpi/scan.c
> +++ b/drivers/acpi/scan.c
> @@ -609,7 +609,8 @@ acpi_bus_get_ejd(acpi_handle handle, acpi_handle *ejd)
> status = acpi_evaluate_object(handle, "_EJD", NULL, &buffer);
> if (ACPI_SUCCESS(status)) {
> obj = buffer.pointer;
> - status = acpi_get_handle(NULL, obj->string.pointer, ejd);
> + status = acpi_get_handle(ACPI_ROOT_OBJECT, obj->string.pointer,
> + ejd);
> kfree(buffer.pointer);
> }
> return status;
>
I can verify that acpi_bus_get_ejd is totally useless without that
patch.
If "status = acpi_evaluate_object(handle, "_EJD", NULL, &buffer);"
succeeds (and AE_NOT_FOUND is not returned), the function will return
AE_BAD_PARAMETER, because NULL never makes sense as first argument of
acpi_get_handle:
status = acpi_get_handle(NULL, obj->string.pointer, ejd);
I can also verify that the correct handle is evaluated with this patch
on a recent ThinkPad, otherwise not.
Please add it, looks like a typo.
Thomas
next prev parent reply other threads:[~2008-02-14 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 12:40 [PATCH] ACPI: Do not pass NULL to acpi_get_handle() when looking for _EJD Holger Macht
2008-02-14 14:49 ` Thomas Renninger [this message]
2008-02-14 15:02 ` Thomas Renninger
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=1203000580.7977.703.camel@queen.suse.de \
--to=trenn@suse.de \
--cc=hmacht@suse.de \
--cc=kristen.c.accardi@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
/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