On Mon, Jun 15, 2015 at 03:17:34PM -0700, Kevin Hilman wrote: > Ard Biesheuvel <[email protected]> writes: > > > On 15 June 2015 at 13:08, Russell King - ARM Linux > [...] > > >> I think the question is - what's caused stable-4.0 to start spitting > >> these errors? Presumably, 4.0 didn't, and stable-4.0 has regressed? > >> Maybe, rather than trying to fix this new regression, the original > >> cause should be reverted? > >> > > > > Not sure whether it's a regression. I think this code does not usually > > get built in Thumb2 mode in the first place. > > It's not a regression in stable-4.0, v4.0 has the same build failure. > > I think we've only caught this now since I added multi_v7 + > CONFIG_THUMB2_KERNEL=y builds to kernelci.org for mainline and the > stable trees.
Okay, so it's not a user reported regression, but comes from a build system. So I continue to wonder what the value is of trying to fix it in stable kernels, vs the risk of de-stabilising them, especially when the fix we have in mainline can't be applied. I'd suggest waiting until we have proper users reporting a failure over this. (Who's a proper user?) -- FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
