From: Kevin Hilman <khilman@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap <linux-omap@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: ARM SoC tree: OMAP PM dependency on tip irq/core
Date: Fri, 30 Sep 2011 06:57:35 -0700 [thread overview]
Message-ID: <87aa9mm8ts.fsf@ti.com> (raw)
Arnd,
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?
Thanks,
Kevin
[1] http://marc.info/?l=linux-omap&m=131684489920440&w=2
[2] http://marc.info/?l=linux-omap&m=131581416908252&w=2
[3] currently here: git://tesla.tglx.de/git/linux-2.6-tip
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM SoC tree: OMAP PM dependency on tip irq/core
Date: Fri, 30 Sep 2011 06:57:35 -0700 [thread overview]
Message-ID: <87aa9mm8ts.fsf@ti.com> (raw)
Arnd,
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?
Thanks,
Kevin
[1] http://marc.info/?l=linux-omap&m=131684489920440&w=2
[2] http://marc.info/?l=linux-omap&m=131581416908252&w=2
[3] currently here: git://tesla.tglx.de/git/linux-2.6-tip
next reply other threads:[~2011-09-30 13:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 13:57 Kevin Hilman [this message]
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-09-30 22:29 ` Kevin Hilman
2011-10-01 20:55 ` Rob Herring
2011-10-01 20:55 ` Rob Herring
2011-10-02 7:03 ` Arnd Bergmann
2011-10-02 7:03 ` Arnd Bergmann
2011-10-06 19:59 ` Tony Lindgren
2011-10-06 19:59 ` Tony Lindgren
2011-10-07 16:04 ` Arnd Bergmann
2011-10-07 16:04 ` Arnd Bergmann
2011-10-07 17:50 ` Kevin Hilman
2011-10-07 17:50 ` Kevin Hilman
2011-10-07 18:53 ` Arnd Bergmann
2011-10-07 18:53 ` Arnd Bergmann
2011-10-07 18:59 ` Thomas Gleixner
2011-10-07 18:59 ` Thomas Gleixner
2011-10-07 20:14 ` Arnd Bergmann
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=87aa9mm8ts.fsf@ti.com \
--to=khilman@ti.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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 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.