From: Bill Davidsen <davidsen@tmr.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Adrian Bunk <bunk@stusta.de>,
Zhang Rui <rui.zhang@intel.com>,
lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] the scheduled ACPI_PROCFS removal
Date: Wed, 11 Jul 2007 13:54:49 -0400 [thread overview]
Message-ID: <46951969.4030109@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707092044520.2887@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Jul 9 2007 17:45, Alan Cox wrote:
>>> This patch contains the scheduled removal of the ACPI procfs interface.
>> What part of "we do not gratuitously break user space interfaces" is so
>> hard for people to understand.
>
> Generally I am with you on that, but if everyone keeps on using /proc --
> and I do[*] -- we will never get rid of it.
>
Is there some reason why you should get rid of it? Is it causing a lot
work to maintain?
>
> [*] Does someone have an alternative for /proc/acpi/battery/BAT1/{state,info}?
>
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-07-11 17:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 14:57 [2.6 patch] the scheduled ACPI_PROCFS removal Adrian Bunk
2007-07-09 15:51 ` Matthew Garrett
2007-07-09 16:45 ` Alan Cox
2007-07-09 18:46 ` Jan Engelhardt
2007-07-09 18:55 ` Matthew Garrett
2007-07-09 22:06 ` Alan Cox
2007-07-11 17:54 ` Bill Davidsen [this message]
2007-07-12 5:32 ` Alexey Starikovskiy
2007-07-12 9:18 ` Richard Hughes
2007-07-12 10:15 ` Alexey Starikovskiy
2007-07-16 5:34 ` Stefan Seyfried
2007-07-10 9:07 ` Zhang Rui
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=46951969.4030109@tmr.com \
--to=davidsen@tmr.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=jengelh@computergmbh.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
/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