linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM SoC tree: OMAP PM dependency on tip irq/core
Date: Fri, 7 Oct 2011 20:59:11 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1110072056050.3240@ionos> (raw)
In-Reply-To: <201110072053.41594.arnd@arndb.de>

On Fri, 7 Oct 2011, Arnd Bergmann wrote:

> On Friday 07 October 2011, Kevin Hilman wrote:
> > > I've pulled in rmk/devel-stable as a dependency now, thanks for
> > > reminding me of that.
> > >
> > > Thomas, where should I get the irq-core branch (or whichever
> > > I should wait for) to pull in as another dependency. Is that
> > > branch one that never gets rebased? 
> > 
> > git://tesla.tglx.de/git/linux-2.6-tip irq/core
> > 
> > I asked Thomas about this earlier when I was going to build up the
> > dependencies myself, and he said it won't be rebased.
> 
> Ok, thanks for the info.
> 
> I think I've now also come up with a workflow for tracking the dependencies:
> I have a depends/xxx branch for each other branch that I need to wait for
> getting merged first. When I want to send a pull request, I first check
> all the depends/* branches using 'git branch --merged next/xxx |
> grep depends' to see what the dependencies are, and 'git branch --merged
> torvalds/master | grep depends' to see if they are already merged upstream.
> When a dependency is already merged, I can remove its tracking branch
> from the arm-soc tree.

For your internal dependecies, yes. But for irq/core you don't have to
wait. You just need to tell Linus in the pull request that you pulled
my branch with my ack as it contains modifications which are
prerequisite for arm/whatever.

When I send my pull request later, then this wont do any damage as
Linus has the commits already. Same the other way round. We do that
all the time, otherwise pull dependencies would be a nightmare.

Thanks,

	tglx

  reply	other threads:[~2011-10-07 18:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30 13:57 ARM SoC tree: OMAP PM dependency on tip irq/core Kevin Hilman
2011-09-30 22:29 ` Kevin Hilman
2011-10-01 20:55   ` Rob Herring
2011-10-02  7:03     ` Arnd Bergmann
2011-10-06 19:59     ` Tony Lindgren
2011-10-07 16:04       ` Arnd Bergmann
2011-10-07 17:50         ` Kevin Hilman
2011-10-07 18:53           ` Arnd Bergmann
2011-10-07 18:59             ` Thomas Gleixner [this message]
2011-10-07 20:14               ` 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=alpine.LFD.2.02.1110072056050.3240@ionos \
    --to=tglx@linutronix.de \
    --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).