All of lore.kernel.org
 help / color / mirror / Atom feed
From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: announcing the clk-next branch
Date: Fri, 27 Apr 2012 11:44:50 +0530	[thread overview]
Message-ID: <4F9A395A.3030306@st.com> (raw)
In-Reply-To: <CAJOA=zOGSh3et4nxE=JdojL4uDjgt8o+oiOU4pmbM=oU2U6prA@mail.gmail.com>

On 4/25/2012 7:02 AM, Turquette, Mike wrote:
> The obvious thing missing are the recent platform ports.  Those folks
> probably want to test on top of this branch first so it seemed
> premature for me to pull them.  After the recent platform ports go in
> then I'll ask for this to head into linux-next.

Hi Mike and others,

I am finding difficulty in creating branch to be pulled in by Mike for clock
stuff. Somebody please help.

SPEAr patches have dependency on few patchsets that are pulled in linux-next
already.
- SPEAr DT support
- SPEAr Pinctrl support
- Mike clk fixes
- Misc Pinctrl patches

Now, how should i create branch for SPEAr clk stuff over these dependencies?
I tried to create a merge of first 3, but couldn't get a linux-next/master
sha of a branch for Last dependency.

Should i cherrypick that one?

At last, i believe this branch, that i would create, must be in a compilable
state? So, i can't just send a pull request for my clock patches rebased over
Mike's branch directly?

-- 
viresh

  parent reply	other threads:[~2012-04-27  6:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25  1:32 announcing the clk-next branch Turquette, Mike
2012-04-25 12:38 ` Sascha Hauer
2012-04-25 12:42   ` Russell King - ARM Linux
2012-04-25 15:15     ` Turquette, Mike
2012-04-26  3:56 ` Viresh Kumar
2012-04-30 14:41   ` Arnd Bergmann
2012-04-30 16:16     ` viresh kumar
2012-04-30 16:37       ` Arnd Bergmann
2012-04-30 16:40         ` viresh kumar
2012-04-30 17:00           ` Arnd Bergmann
2012-04-27  4:10 ` Viresh Kumar
2012-04-27  6:14 ` Viresh Kumar [this message]
2012-04-27  7:09   ` Shawn Guo
2012-04-27 17:54     ` Turquette, Mike
2012-04-28  4:52       ` Shawn Guo
2012-04-30 14:43       ` Arnd Bergmann

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=4F9A395A.3030306@st.com \
    --to=viresh.kumar@st.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.