Hi Mike,

On Tue, 26 Jun 2012 16:05:03 -0700 Mike Turquette [off-list ref] 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 at canb.auug.org.au
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120628/c338de11/attachment.sig>