Hi Stephen, On Fri, Nov 6, 2015 at 2:19 PM, Stephen Rothwell <[email protected]> wrote:
> On Fri, 6 Nov 2015 10:36:34 -0800 Kevin Hilman <[email protected]> wrote: >> >> On Fri, Nov 6, 2015 at 8:13 AM, Sebastian Reichel <[email protected]> wrote: >> > This reverts commit af19161aaed7ff8d1a52b2e517460f2fa0774e32, >> > which breaks the omap3 device tree build due to a wrong reference. >> > >> > I accidently queued this change via the power supply subsystem while >> > telling Marek at the same time, that it should go through Tony's tree. >> > Following that I did miss Stephen's messages about the build failure in >> > linux-next and since he switched to merging an older snapshot nobody >> > else noticed the problem in my tree. I didn't notice myself, since I >> > did not build any device tree files assuming none have changed by me. >> > >> > Signed-off-by: Sebastian Reichel <[email protected]> >> >> We also found this in kernelci.org build testing, and verified that >> this fixes the build. >> >> Tested-by: Kevin Hilman <[email protected]> >> >> Thanks Felipe for reporting, and thanks Sebastian for the quick fix. > > I think "quick fix" is a bit rich. You're right, sorry. I didn't have the full context. I wasn't fully aware of the history in -next of this problem. I just found it when it ended up in mainline. I don't think the problem was not getting your emails, looks like the problem was a major disconnect between what was sent to Linus and what was in -next. :( Hopefully this snafu will help prevent that in the future, Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
