linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mturquette@ti.com (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: adding the common clk tree
Date: Mon, 25 Jun 2012 18:55:51 -0700	[thread overview]
Message-ID: <20120626015551.GW4402@gmail.com> (raw)

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

             reply	other threads:[~2012-06-26  1:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26  1:55 Mike Turquette [this message]
2012-06-26  3:25 ` linux-next: adding the common clk tree Stephen Rothwell
2012-06-26 23:05   ` Mike Turquette
2012-06-27 14:29     ` Stephen Rothwell
2012-06-27 17:50       ` Mike Turquette
2012-06-30 19:47 ` Linus Walleij
2012-07-02 23:33   ` Stephen Rothwell
2012-07-03  1:33     ` Turquette, Mike
2012-07-03  1:49 ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120626015551.GW4402@gmail.com \
    --to=mturquette@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).