linux-kernel - Re: [PATCH 0/13] Updated V4

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]

Date:	Fri, 2 May 2008 16:52:48 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Liam Girdwood <lg@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk,
	broonie@...nsource.wolfsonmicro.com
Subject: Re: [PATCH 0/13] Updated V4  - Regulator Framework

On Fri, 02 May 2008 16:40:41 +0100
Liam Girdwood <lg@...nsource.wolfsonmicro.com> wrote:

> This is an updated version of the kernel voltage & current regulator
> framework based on comments received from version 3 of the patch series.
> 
> The regulator framework is designed to provide a standard kernel
> interface to control voltage and current regulators on SoC based
> systems.
> 
> The intention is to allow systems to dynamically control regulator power
> output in order to save power and prolong battery life. This applies to
> both voltage regulators (where voltage output is controllable) and
> current sinks (where current limit is controllable).
> 

oh gee.

I (and others) reviewed and commented on all this code last month.  Now
here it is again and, although I'm sure it is delightful code, nobody wants
to have to read it all again ;)

The one-month gap between v3 and v4 is unfortunate.  It means that everyone
has forgotten everything.


Was all the review feedback satisfactorily handled to the reviewers'
satisfaction?

Is there any new material in here which would require a re-review?
--
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/