From: Paul Ionescu <i_p_a_u_l-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC] dev_acpi: device driver for userspace access to ACPI
Date: Sat, 14 Aug 2004 22:59:15 +0300 [thread overview]
Message-ID: <pan.2004.08.14.19.59.14.836975@yahoo.com> (raw)
In-Reply-To: 1091721177.3837.39.camel@tdi
On Thu, 05 Aug 2004 09:52:56 -0600, Alex Williamson wrote:
> If the sysfs version isn't making too many people cringe, I'd prefer
> to pursue that direction. Here's a pointer to the last version I
> posted:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=108239031314885&w=2
>
> I also attached the latest version I have below, it's newer, but still
> dated from April. I believe it still applies and works. let me know if
> you think it has a chance. Thanks,
>
> Alex
Hi Alex,
Do you have any news about your patch for ACPI userspace access ?
Did you received feedback form anybody else except Greg ?
How is going to be in the end, /sys/ interface or /dev/acpi ?
Thanks,
Paul
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
prev parent reply other threads:[~2004-08-14 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 17:00 [RFC] dev_acpi: device driver for userspace access to ACPI Alex Williamson
2004-08-03 17:31 ` Dave Hansen
2004-08-03 18:17 ` Alex Williamson
2004-08-03 18:34 ` Dave Hansen
2004-08-03 21:02 ` Alex Williamson
2004-08-05 4:36 ` Greg KH
[not found] ` <20040805043636.GA28244-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2004-08-05 15:52 ` Alex Williamson
2004-08-14 19:59 ` Paul Ionescu [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=pan.2004.08.14.19.59.14.836975@yahoo.com \
--to=i_p_a_u_l-/e1597as9lqavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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