From: Stefan Seyfried <seife@suse.de>
To: Richard Hughes <hughsient@gmail.com>
Cc: Alexey Starikovskiy <aystarik@gmail.com>,
Bill Davidsen <davidsen@tmr.com>,
Jan Engelhardt <jengelh@computergmbh.de>,
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: Mon, 16 Jul 2007 07:34:32 +0200 [thread overview]
Message-ID: <20070716053432.GA20102@suse.de> (raw)
In-Reply-To: <1184231897.2380.2.camel@work>
On Thu, Jul 12, 2007 at 10:18:17AM +0100, Richard Hughes wrote:
> On Thu, 2007-07-12 at 09:32 +0400, Alexey Starikovskiy wrote:
> > >> [*] Does someone have an alternative for
> > >> /proc/acpi/battery/BAT1/{state,info}?
> > I'm working on it. Should have proto by the end of week.
>
> If you are using the power_supply class (i hope you are ;-) then a HAL
> from freedesktop git should make userspace continue to just work.
Having to update HAL is not my definition of "does not break userspace".
And, BTW, there is more than just HAL out there using /proc/acpi, and
this should continue to work.
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2007-07-16 6:39 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
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 [this message]
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=20070716053432.GA20102@suse.de \
--to=seife@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=aystarik@gmail.com \
--cc=bunk@stusta.de \
--cc=davidsen@tmr.com \
--cc=hughsient@gmail.com \
--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