From: Arnd Bergmann <arnd@arndb.de>
To: Rob Herring <robherring2@gmail.com>
Cc: Kevin Hilman <khilman@ti.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: ARM SoC tree: OMAP PM dependency on tip irq/core
Date: Sun, 02 Oct 2011 09:03:58 +0200 [thread overview]
Message-ID: <1988740.uJMkcEa7Kl@wuerfel> (raw)
In-Reply-To: <4E877E29.7000309@gmail.com>
On Saturday 01 October 2011 15:55:05 Rob Herring wrote:
> >
> > Kevin Hilman <khilman@ti.com> writes:
> >
> >> The upcoming OMAP4 PM series from Santosh[1] that we're planning to
> >> queue for v3.2 has a dependency[2] on a patch currently queued for v3.2
> >> in the irq/core branch of Thomas' tip tree[3].
> >>
> >> In the past, I noticed you merged external trees like this to solve
> >> dependencies.
> >>
> >> Could you pull the irq/core branch into your tree to meet this
> >> dependency?
> >
> > On second thought, since Santosh's branch is the only one with this
> > dependency (and we also have a dependency on Russell's devel-stable)
> > I'll just build up a branch for Santosh's series that includes
> > rmk/devel-stable and tglx/irq-core.
> >
>
> Any new platforms will have a dependency on rmk/devel-stable with the
> mach header clean-up. I'll probably have a dependency on tglx's tree as
> well.
Good point. Also, I think in general it's better if I try to keep track
of the depencies myself, so I don't accidentally submit patches upstream
that belong into someone else's realm.
I haven't come up with a good scheme for that yet. Right now I just
add a depends/* branch and try to remember which branches depend on
that. If it gets harder than this, I'll have to write it down somewhere,
but it would be nice to have some tool that can automatically warn
if I try to submit something that has an unfulfilled dependency.
Arnd
next prev parent reply other threads:[~2011-10-02 7:04 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 [this message]
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
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=1988740.uJMkcEa7Kl@wuerfel \
--to=arnd@arndb.de \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=robherring2@gmail.com \
--cc=tglx@linutronix.de \
/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