Hi Kevin, On Fri, 6 Nov 2015 10:36:34 -0800 Kevin Hilman <khil...@kernel.org> wrote: > > On Fri, Nov 6, 2015 at 8:13 AM, Sebastian Reichel <s...@kernel.org> 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 <s...@kernel.org> > > We also found this in kernelci.org build testing, and verified that > this fixes the build. > > Tested-by: Kevin Hilman <khil...@linaro.org> > > Thanks Felipe for reporting, and thanks Sebastian for the quick fix.
I think "quick fix" is a bit rich. I reported this to Sebastian on Sept 29, Oct 2 , Oct 8, Oct 16, and Oct 21. The only response I got was from Marek Belisko on Oct 8 and 21. I have been using the battery tree (git://git.infradead.org/battery-2.6.git#master) from Sept 25, so none of the commits after that have been in any linux-next release. Yes, I am a little annoyed. Do people have trouble receiving my emails? -- Cheers, Stephen Rothwell s...@canb.auug.org.au -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
