From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Deepa Dinamani <deepa.kernel@gmail.com>,
heiko.carstens@de.ibm.com
Subject: linux-next: build failure after merge of the y2038 tree
Date: Fri, 16 Mar 2018 13:25:29 +1100 [thread overview]
Message-ID: <20180316132529.45126501@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
Hi Arnd,
After merging the y2038 tree, today's linux-next build (s390 allnoconfig)
failed like this:
In file included from include/linux/elf.h:5:0,
from include/linux/module.h:15,
from init/main.c:16:
arch/s390/include/asm/elf.h:138:1: error: unknown type name 's390_compat_regs'
Caused by commit
f00689038f71 ("include: Move compat_timespec/ timeval to compat_time.h")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-03-16 2:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 2:25 Stephen Rothwell [this message]
2018-03-16 5:23 ` linux-next: build failure after merge of the y2038 tree Deepa Dinamani
2018-03-16 8:14 ` Arnd Bergmann
2018-03-17 23:09 ` [PATCH] s390: Use asm/compat.h instead of linux/compat.h Deepa Dinamani
2018-03-17 23:13 ` linux-next: build failure after merge of the y2038 tree Deepa Dinamani
-- strict thread matches above, loose matches on Subject: below --
2018-03-27 7:26 Stephen Rothwell
2018-12-17 9:11 Stephen Rothwell
2018-12-17 12:49 ` Arnd Bergmann
2018-12-17 22:25 ` Steve French
2019-11-14 4:38 Stephen Rothwell
2019-11-14 12:10 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180316132529.45126501@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox