public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <aystarik@gmail.com>
To: Richard Hughes <hughsient@gmail.com>
Cc: 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: Thu, 12 Jul 2007 14:15:26 +0400	[thread overview]
Message-ID: <4695FF3E.60307@gmail.com> (raw)
In-Reply-To: <1184231897.2380.2.camel@work>

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. Please
> yell if you notice any differences.
Well, both SBS and CM batteries were able to set an alarm capacity. 
I did not found write capability to property in power_supply class yet.
So consider this a yelling :)

Thanks,
Alex.

  reply	other threads:[~2007-07-12 10:15 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 [this message]
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=4695FF3E.60307@gmail.com \
    --to=aystarik@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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