From: "Randy.Dunlap" <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
To: Randy Dunlap <randy_d_dunlap-VuQAYsv1563Yd54FQh9/CA@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/1] make acpi_path_name() global (v4)
Date: Mon, 26 Dec 2005 19:45:48 -0800 [thread overview]
Message-ID: <20051226194548.4a5cc0df.rdunlap@xenotime.net> (raw)
In-Reply-To: <20051221120500.0621a7a2.randy_d_dunlap-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Hi--
You can drop this patch. With the changes wanted by everyone
(except for Pat Mochel), this just makes acpi_path_name() be
a synonym for acpi_get_name(), so I'll just use acpi_get_name()
directly.
On Wed, 21 Dec 2005 12:05:00 -0800 Randy Dunlap wrote:
> From: Randy Dunlap <randy_d_dunlap-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
>
> Make acpi_path_name() usable by everyone.
> I need this for adding SATA suspend/resume ACPI support.
>
> v4: Fix enter/exit trace error noted by Matthew Wilcox.
> v3: use EXPORT_SYMBOL_GPL for acpi_path_name.
> v2: use ACPI-CA calling convention for name buffer.
---
~Randy
-------------------------------------------------------
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-27 3:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 20:05 [PATCH 1/1] make acpi_path_name() global (v4) Randy Dunlap
[not found] ` <20051221120500.0621a7a2.randy_d_dunlap-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2005-12-27 3:45 ` Randy.Dunlap [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=20051226194548.4a5cc0df.rdunlap@xenotime.net \
--to=rdunlap-/uha2rfvqtnk1umjsbkqmq@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=randy_d_dunlap-VuQAYsv1563Yd54FQh9/CA@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