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: Thu, 26 Apr 2012 09:26:48 +0530	[thread overview]
Message-ID: <4F98C780.8020309@st.com> (raw)
In-Reply-To: <CAJOA=zOGSh3et4nxE=JdojL4uDjgt8o+oiOU4pmbM=oU2U6prA@mail.gmail.com>

On 4/25/2012 7:02 AM, Turquette, Mike wrote:
> Hi all,
> 
> The clock patches that I have signed-off on and picked from the list
> are all rebased on top of 3.4-rc4.  They can be found here:
> 
> git://git.linaro.org/people/mturquette/linux.git clk-next
> 
> If the branch is missing anything that I have ACK'd then please let me know.
> 
> 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.

I want to understand a bit about how these patches go to linux-next.
Mike would be sleeping right now, so will not disturb him ;)

Arnd,

Can you please help?

Just like Mike, you also asked me to base my patches on an rc release.
Now, few of the dependency patches are there in linux-next that i would need.
Some under my authorship, and some from others. And this number can be 30-50.

Should i ask Mike to apply all of them first and then my patches OR do that
myself and send a pull request. Which would mean all patches, that weren't
related to my patchset also get pushed through my branch. Isn't that a problem?

-- 
viresh

  parent reply	other threads:[~2012-04-26  3:56 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 [this message]
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
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=4F98C780.8020309@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.