On Wed, Apr 11, 2018 at 9:32 PM, Eric W. Biederman <ebied...@xmission.com> wrote: > Arnd Bergmann <a...@arndb.de> writes: > >> We have several files on sparc that include linux/compat.h and expect >> asm/compat.h not to be included, otherwise we get a build failure. > > Should this say: "We have several files on sparc that include > linux/compat.h and expect asm/compat.h not be included when > !CONFIG_COMPAT." ?
Correct, I'll fix it up. I'll say '32-bit builds' instead, which is what I'm interested in. On sparc64, CONFIG_COMPAT is enabled unconditionally, so it's really the same thing. > I don't have your tree and I see asm/compat.h included from > linux/compat.h already so the description above seems wrong. I removed the tree from linux-next before the merge window because of this build regression, if you are interested in the other changes, please see git://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git y2038-next Arnd _______________________________________________ Y2038 mailing list Y2038@lists.linaro.org https://lists.linaro.org/mailman/listinfo/y2038