On Saturday 01 October 2011 15:55:05 Rob Herring wrote: > > > > Kevin Hilman <khilman@xxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
