linux-kernel - Re: [PATCH 3/5] power_supply: add a TRICKLE_CHARGING status, and add it to the olpc driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090624100911.GB21919@sirena.org.uk>
Date:	Wed, 24 Jun 2009 11:09:12 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	"Richard A. Smith" <richard@...top.org>
Cc:	Andres Salomon <dilinger@...labora.co.uk>, cbou@...l.ru,
	dwmw2@...radead.org, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Paul Fox <pgf@...top.org>, dsaxena@...top.org
Subject: Re: [PATCH 3/5] power_supply: add a TRICKLE_CHARGING status, and
	add it to the olpc driver

On Tue, Jun 23, 2009 at 07:46:26PM -0400, Richard A. Smith wrote:
> Mark Brown wrote:

>> 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.

The other thing that has a reasonable number of users is the in-kernel
APM emulation - when I last looked quite a few users were using that
still.

I'd expect that either HAL or things that use it would need to know
about the new state to do something sensible with it.  All the widely
deployed users should be using those, I don't recall any of the other
things I found being things that I'd particularly heard of.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/