From: Matthew Wilcox <matthew-Ztpu424NOJ8@public.gmane.org>
To: "Randy.Dunlap" <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
pcihpd-discuss-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
kristen.c.accardi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
gregkh-l3A5Bk7waGM@public.gmane.org,
robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH 1/2] make acpi_path_name() global (v3)
Date: Wed, 21 Dec 2005 05:44:54 -0700 [thread overview]
Message-ID: <20051221124454.GA2361@parisc-linux.org> (raw)
In-Reply-To: <20051220191828.65d0087f.rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
On Tue, Dec 20, 2005 at 07:18:28PM -0800, Randy.Dunlap wrote:
> +acpi_status acpi_path_name(acpi_handle handle, struct acpi_buffer *namebuf)
> +{
> + acpi_status status;
> +
> + status = acpi_get_name(handle, ACPI_FULL_PATHNAME, namebuf);
> +
> + return_ACPI_STATUS(status);
> +}
> +EXPORT_SYMBOL_GPL(acpi_path_name);
Nope. You either need to add an "ACPI_FUNCTION_TRACE" call at the top
of your function, or just do "return status;". Otherwise you'll screw
up the ACPI debug code.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
prev parent reply other threads:[~2005-12-21 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 3:18 [PATCH 1/2] make acpi_path_name() global (v3) Randy.Dunlap
[not found] ` <20051220191828.65d0087f.rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2005-12-21 12:44 ` Matthew Wilcox [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=20051221124454.GA2361@parisc-linux.org \
--to=matthew-ztpu424noj8@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=gregkh-l3A5Bk7waGM@public.gmane.org \
--cc=kristen.c.accardi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=pcihpd-discuss-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org \
--cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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