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:	Tue, 29 Jul 2008 21:33:46 +0100
From:	Liam Girdwood <lg@...nsource.wolfsonmicro.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	arm kernel <linux-arm-kernel@...ts.arm.linux.org.uk>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org
Subject: Re: [PATCH 0/13] Updated V4  - Regulator Framework

On Thu, 2008-07-10 at 02:08 -0700, Andrew Morton wrote:
> 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.
> 
> git-regulator.patch has been in -mm for two months without incident.  I'd
> forgotten about it.   This is bad - we should have put it into linux-next.
> 
> If you hope to get this into 2.6.27 then please send the git URL to Stephen
> and the linux-next list asap.  Please also resend the patches to this list
> for re-review.  Then, if it doesn't get shot down, send Linux a pull
> request during the 2.6.27 merge window.  ie: about one week from today.

Would there be any chance of this going in for rc2 ? (2 pull requests
sent recently prior to rc1) or would it be better now waiting for the
2.6.28 merge window ?

Thanks

Liam

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