Hi Geert, Hi Linus, On Tue, Mar 10, 2015 at 10:30:54AM +0100, Geert Uytterhoeven wrote: > Hi Simon, > > On Tue, Mar 10, 2015 at 8:55 AM, Simon Horman <[email protected]> wrote: > > I have observed what appears to be a regression in next-20150310. Using > > the shmobile_defconfig the lager board does not produce console output > > whatsoever. If I revert bfb6698fad74e7ba2 ("pinctrl: sh-pfc: r8a7790: > > Remove non existing GPIO pins") then the problem seems to be resolved. > > > > Likewise for the koelsh board and 896498d439cec6ff0 ("pinctrl: sh-pfc: > > r8a7791: Remove non existing GPIO pins"). > > That's correct. I reverted these in renesas-drivers-2015-03-09-v4.0-rc3. > > In the mean time, they have been dropped from pinctrl/for-next, as > requested by Laurent last week. > > Sorry for the issues.
On Tue, Mar 10, 2015 at 03:00:05PM +0100, Linus Walleij wrote: > On Tue, Mar 10, 2015 at 8:55 AM, Simon Horman <[email protected]> wrote: > > > I have observed what appears to be a regression in next-20150310. Using > > the shmobile_defconfig the lager board does not produce console output > > whatsoever. If I revert bfb6698fad74e7ba2 ("pinctrl: sh-pfc: r8a7790: > > Remove non existing GPIO pins") then the problem seems to be resolved. > > I have removed these two patches from the tree since last night. Thanks, for the quick responses. I'll be happy to see next working again :) -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
