On Fri, Jun 28, 2013 at 01:05:42PM -0700, Olof Johansson wrote: > On Fri, Jun 28, 2013 at 1:03 PM, Maxime Ripard > <maxime.rip...@free-electrons.com> wrote: > > On Fri, Jun 28, 2013 at 06:15:32PM +0100, Lorenzo Pieralisi wrote: > >> The patch above should already be queued in next/dt right ? > > > > Indeed. > > > > Then why the latest patch of your patchset got in 3.10, while the > > patches actually fixing the DT it would have impacted were delayed to > > 3.11? > > > > (And why was it merged so late in the development cycle?) > > This. So now we have to scramble because some device trees will > produce warnings at boot. > > Russell, the alternative is to revert Lorenzo's patch for 3.10 (and > re-introduce it for 3.11). Do you have a preference?
Sorry but I really don't understand what all the fuss in this thread is about. This thread seems to be saying that two development patches were merged, which were 7762/1 and 7763/1, and that 7764/1 is a fix? Are you sure about that, because that's not how they're described, and not how they look either. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
