From: "Richard A. Smith" <richard@laptop.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Andres Salomon <dilinger@collabora.co.uk>,
cbou@mail.ru, dwmw2@infradead.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Paul Fox <pgf@laptop.org>,
dsaxena@laptop.org
Subject: Re: [PATCH 3/5] power_supply: add a TRICKLE_CHARGING status, and add it to the olpc driver
Date: Tue, 23 Jun 2009 19:46:26 -0400 [thread overview]
Message-ID: <4A416952.2050809@laptop.org> (raw)
In-Reply-To: <20090623232537.GE16188@opensource.wolfsonmicro.com>
Mark Brown wrote:
> On Tue, Jun 23, 2009 at 07:13:17PM -0400, Richard A. Smith wrote:
>> Mark Brown wrote:
>
>>> A separate file with the detailed information would sidestep this since
>>> it's a new interface. I'm not strongly opposed to adding the new states
>>> but I do think it's worth considering other ways of doing this.
>
>> I've got no problems with a new interface. But, i'm also not the person
>> writing the driver. :)
>
> It's really no bother from the driver point of view either way, it's the
> user space applications that are the concern here - are they going to
> cope well with a new state appearing there?
I can only speak for OLPC's usage. But my script, the documentation on
our wiki, and HAL are the only things that I know of that use that info
and none of them should have any problem with it changing.
--
Richard Smith <richard@laptop.org>
One Laptop Per Child
next prev parent reply other threads:[~2009-06-23 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 3:46 [PATCH 3/5] power_supply: add a TRICKLE_CHARGING status, and add it to the olpc driver Andres Salomon
2009-06-23 10:37 ` Mark Brown
2009-06-23 19:28 ` Richard A. Smith
2009-06-23 22:44 ` Mark Brown
2009-06-23 23:13 ` Richard A. Smith
2009-06-23 23:25 ` Mark Brown
2009-06-23 23:46 ` Richard A. Smith [this message]
2009-06-24 10:09 ` Mark Brown
2009-06-30 6:20 ` Andres Salomon
2009-06-24 14:40 ` Anton Vorontsov
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=4A416952.2050809@laptop.org \
--to=richard@laptop.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cbou@mail.ru \
--cc=dilinger@collabora.co.uk \
--cc=dsaxena@laptop.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgf@laptop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox