linux-kernel - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Jun 2012 00:29:25 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Mike Turquette <mturquette@...com>
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: Re: linux-next: adding the common clk tree

Hi Mike,

On Tue, 26 Jun 2012 16:05:03 -0700 Mike Turquette <mturquette@...com> wrote:
>
> So please let me know if I still have the concept wrong and I'll change
> things up.  Otherwise my clk-next fulfils all of the guidelines you've
> mentioned below for inclusion into linux-next.

OK, that all seems to be fine.  I would make one suggestion: that you
create the clk-next branch like this:

git checkout clk-next
git reset --hard clk-3.x
git merge clk-fixes
git am patches/clk/next/incoming/*.patch

or maybe just merge clk-fixes directly into clk-3.x when necessary or
from time to time and base clk-next just in clk-3.x.
--
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped