From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Cc: acpi-devel@lists.sourceforge.net
Subject: Re: ACPI buttons in 2.6.12-rc4-mm2
Date: Fri, 29 Jul 2005 12:35:43 -0400 [thread overview]
Message-ID: <42EA5ADF.9000202@tmr.com> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B300428C952@hdsmsx401.amr.corp.intel.com>
Brown, Len wrote:
> I agree that the value of _LID can be usefult to user-space
> and I'll be sure it is restored as a property of the lid device
> under sysfs -- available as a simple file read like it
> was under /proc.
You're missing the point, removing the /proc feature breaks existing
code. You can add new features in /sys as you like, but when you remove
existing featires you break system for no benefit.
WARNING: multiple messages have this Message-ID (diff)
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Cc: acpi-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: ACPI buttons in 2.6.12-rc4-mm2
Date: Fri, 29 Jul 2005 12:35:43 -0400 [thread overview]
Message-ID: <42EA5ADF.9000202@tmr.com> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B300428C952@hdsmsx401.amr.corp.intel.com>
Brown, Len wrote:
> I agree that the value of _LID can be usefult to user-space
> and I'll be sure it is restored as a property of the lid device
> under sysfs -- available as a simple file read like it
> was under /proc.
You're missing the point, removing the /proc feature breaks existing
code. You can add new features in /sys as you like, but when you remove
existing featires you break system for no benefit.
next prev parent reply other threads:[~2005-07-29 16:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 20:49 Re: ACPI buttons in 2.6.12-rc4-mm2 Brown, Len
2005-07-27 20:49 ` [ACPI] " Brown, Len
2005-07-29 16:35 ` Bill Davidsen [this message]
2005-07-29 16:35 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2005-07-27 23:40 Brown, Len
2005-07-27 23:40 ` Brown, Len
2005-07-27 23:19 Brown, Len
2005-07-27 23:19 ` Brown, Len
[not found] ` <F7DC2337C7631D4386A2DF6E8FB22B300428CA9E-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-07-27 23:26 ` Andrew Morton
2005-07-27 23:26 ` Andrew Morton
2005-05-22 11:25 Cameron Harris
[not found] ` <b6d0f5fb0505220425146d481a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-07-26 19:44 ` Len Brown
2005-07-26 19:44 ` Len Brown
[not found] ` <1122407079.13241.4.camel-g3qfMnKXm6m1ouK1UO9oVVDQ4js95KgL@public.gmane.org>
2005-07-26 19:55 ` Matthew Garrett
2005-07-26 19:55 ` Matthew Garrett
2005-07-27 23:09 ` Andrew Morton
2005-07-27 23:09 ` Andrew Morton
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=42EA5ADF.9000202@tmr.com \
--to=davidsen@tmr.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@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.