On 8 October 2014 20:28, Arnd Bergmann <arnd@xxxxxxxx> wrote: > On Wednesday 08 October 2014 08:29:16 Doug Anderson wrote: >> >> On Wed, Oct 8, 2014 at 8:20 AM, Arnd Bergmann <arnd@xxxxxxxx> wrote: >> > Why does it cause a regression though? Does this mean you are breaking >> > any boot with an old DT file and a new kernel? That would be very >> > bad, the driver is supposed to keep working with an existing dtb. >> >> The old dts file specified completely the wrong regulator. It >> happened that the old code didn't really care, but when the code was >> fixed to care then things broke. If we need to keep old dts files >> working then the most sensible place to do it would be in a "fixup old >> broken device trees" stage somewhere in kernel boot. > > Ok, got it. I guess it's better to apply this one first then. > > Arnd Thanks for your comments Arnd! I have applied this once to my mmc tree now. Please tell me soon if you want to carry this through arm-soc instead, thus I can drop it. Kind regards Uffe -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
