linux-kernel - linux-next: adding the common clk 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-next>] [day] [month] [year] [list]

Message-ID: <20120626015551.GW4402@gmail.com>
Date:	Mon, 25 Jun 2012 18:55:51 -0700
From:	Mike Turquette <mturquette@...com>
To:	sfr@...b.auug.org.au
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	broonie@...nsource.wolfsonmicro.com, rnayak@...com,
	viresh.kumar@...aro.org, amit.kucheria@...aro.org,
	linus.walleij@...ricsson.com, shawn.guo@...escale.com,
	mkl@...gutronix.de, sr@...x.de, pawel.moll@....com,
	maxime.ripard@...e-electrons.com, linux@....linux.org.uk,
	arnd.bergmann@...aro.org, olof@...om.net
Subject: linux-next: adding the common clk tree

Hi Stephen,

Would you please add the clk-next branch of the common clock tree to
linux-next?

git://git.linaro.org/people/mturquette/linux.git clk-next

Thanks much!

For all of those Cc'd, I just wanted to say that I'm changing the way I
manage clk-next.  The clk-next branch now WILL be rebased, and it's only
purpose is to make it easy to test things in linux-next.  You can base
work on it, but be prepare for breakage and shifting commit ids.

If you don't want breakage and shifting commit ids then you might want
to use my clk-fixes branch (stable) and my clk-3.x branch (stable).  As
patches go through the linux-next cycle and appear stable I'll migrate
them over to clk-3.x which won't ever be rebased.  This is the branch
I'll send to Linus.  clk-next is simply comprised of merging clk-fixes,
clk-3.x and whatever unstable patches I have laying around.

Regards,
Mike
--
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/