linux-kernel - Re: Temporary relocation of the regulator tree

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: <20111007123842.GF14518@opensource.wolfsonmicro.com>
Date:	Fri, 7 Oct 2011 13:38:43 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Liam Girdwood <lrg@...com>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Temporary relocation of the regulator tree

On Fri, Oct 07, 2011 at 11:36:07PM +1100, Stephen Rothwell wrote:
> On Fri, 7 Oct 2011 12:40:46 +0100 Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:

> > Due to a combination of the kernel.org downtime and an intensely busy
> > time at work for Liam can you please change the regulator tree in -next
> > to be:

> > 	git://opensource.wolfsonmicro.com/regulator.git for-next

> > until Liam manages to get sufficient free time to keep up with the day
> > to day flow again.

> OK, I will switch to that tree from Tuesday (Monday is a holiday) unless
> Liam screams.  I have also added you as a contact for this tree (called
> voltage in linux-next - would it be better to call it regulator?).

It should be called regulator, the code is all called regulator.  I
never understood why you'd labelled it voltage :)
--
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/