From: Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
To: Alex Williamson <alex.williamson-VXdhtT5mjnY@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC] dev_acpi: device driver for userspace access to ACPI
Date: Wed, 4 Aug 2004 21:36:37 -0700 [thread overview]
Message-ID: <20040805043636.GA28244@kroah.com> (raw)
In-Reply-To: <1091552426.4981.103.camel@tdi>
On Tue, Aug 03, 2004 at 11:00:26AM -0600, Alex Williamson wrote:
>
> Populating the sysfs tree didn't seem to generate as much interest as
> I'd hoped and I don't think it kept with the spirit of sysfs very well.
I'm sorry if I didn't speak up at the time, but I still think that your
sysfs patches were the right way to go. Why do you think they don't
keep with the spirit of sysfs? Do you have a pointer to your last
patch that exported the acpi table info through sysfs?
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
next prev parent reply other threads:[~2004-08-05 4:36 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 [this message]
[not found] ` <20040805043636.GA28244-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2004-08-05 15:52 ` Alex Williamson
2004-08-14 19:59 ` Paul Ionescu
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=20040805043636.GA28244@kroah.com \
--to=greg-u8xffu+wg4eavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=alex.williamson-VXdhtT5mjnY@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