From: Nico Golde <nion@gmx.net>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: inconsistency in /proc/acpi directory structure?
Date: Thu, 9 Aug 2007 19:45:28 +0200 [thread overview]
Message-ID: <20070809174528.GA7282@ngolde.de> (raw)
In-Reply-To: <200708091202.54943.lenb@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
Hi,
* Len Brown <lenb@kernel.org> [2007-08-09 19:25]:
> I have to second what Henrique wrote.
> Please avoid /proc/acpi/* whenever you can can.
> We are trying to get rid of it completely,
> but that is only partly done.
I know about that and it's a typical kernel hacker argument,
but don't forget people want to have working software in the
meantime of your switch ;)
> I really resist changes to /proc/acpi/* because
> I consider it legacy and would rather the effort
> be focused on the new sysfs interfaces.
I will switch step by step. From what I can see not really
much things apart from the acpi version already switched to
sysfs. Maybe I missed it. I will answer in detail on
Henriques mail hopefully tomorrow.
Kind regards and thanks for your quick replies
Nico
--
Nico Golde - http://ngolde.de - nion@jabber.ccc.de - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-08-09 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 12:39 inconsistency in /proc/acpi directory structure? Nico Golde
2007-08-09 12:54 ` Henrique de Moraes Holschuh
2007-08-09 13:15 ` Henrique de Moraes Holschuh
2007-08-09 16:02 ` Len Brown
2007-08-09 17:45 ` Nico Golde [this message]
2007-08-09 22:49 ` Len Brown
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=20070809174528.GA7282@ngolde.de \
--to=nion@gmx.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.