From: Len Brown <lenb@kernel.org>
To: Nico Golde <nion@gmx.net>
Cc: linux-acpi@vger.kernel.org
Subject: Re: inconsistency in /proc/acpi directory structure?
Date: Thu, 9 Aug 2007 18:49:54 -0400 [thread overview]
Message-ID: <200708091849.54850.lenb@kernel.org> (raw)
In-Reply-To: <20070809174528.GA7282@ngolde.de>
On Thursday 09 August 2007 13:45, Nico Golde wrote:
> 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
Things which have switched are now under CONFIG_ACPI_PROCFS in 2.6.23.
When more things switch in the future, they'll go there too.
If you have a specific suggestion for a bug fix to /proc/acpi/*,
please let me know, or better yet, send a patch.
-Len
prev parent reply other threads:[~2007-08-09 22:50 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
2007-08-09 22:49 ` Len Brown [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=200708091849.54850.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=nion@gmx.net \
/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.