| 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
| ||
|
Message-ID: <20090623232537.GE16188@opensource.wolfsonmicro.com> Date: Wed, 24 Jun 2009 00:25:38 +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: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? > Suggestions on what it would look like? Probably another sysfs file in the same directory, I'd imagine. -- 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/
Powered by blists - more mailing lists