From: John Paul Adrian Glaubitz <glaubitz@xxxxxxxxxxxxxxxxxxx> Date: Mon, 10 Jul 2017 20:35:21 +0200 > On Mon, Jul 10, 2017 at 07:32:27PM +0100, David Miller wrote: >> Yes, let's make sure that 32-bit userland support in the kernel gets >> even less testing, and gets even buggier over time. > > My point was not 32-bit vs. 64-bit, my point was using an outdated > userland from 2015. For 32-bit tests, I'd rather create a Gentoo > a 32-bit sparc chroot or rebootstrap Debian sparc. My userland is from 2013 with random built-from-src pieces of updated tools and glibc, should I just throw my hands up in the air when the kernel OOPSes and not look into it at all? None of this makes any sense at all. If a bug shows up in the kernel between X and Y, it doesn't matter if it triggers with an old userland or a new one. It should be investigated just the same. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
