From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Russell King <linux@armlinux.org.uk>
Cc: Quanyang Wang <quanyang.wang@windriver.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the arm tree
Date: Tue, 26 Oct 2021 10:25:36 +1100 [thread overview]
Message-ID: <20211026102536.31e5ab62@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]
Hi all,
After merging the arm tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from <command-line>:
arch/arm/mm/mmu.c: In function 'early_fixmap_init':
include/linux/compiler_types.h:328:38: error: call to '__compiletime_assert_295' declared with attribute error: BUILD_BUG_ON failed: (__fix_to_virt(__end_of_fixmap_region) >> PMD_SHIFT) != FIXADDR_TOP >> PMD_SHIFT
328 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^
include/linux/compiler_types.h:309:4: note: in definition of macro '__compiletime_assert'
309 | prefix ## suffix(); \
| ^~~~~~
include/linux/compiler_types.h:328:2: note: in expansion of macro '_compiletime_assert'
328 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^~~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:39:37: note: in expansion of macro 'compiletime_assert'
39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
| ^~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:50:2: note: in expansion of macro 'BUILD_BUG_ON_MSG'
50 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
| ^~~~~~~~~~~~~~~~
arch/arm/mm/mmu.c:372:2: note: in expansion of macro 'BUILD_BUG_ON'
372 | BUILD_BUG_ON((__fix_to_virt(__end_of_fixmap_region) >> PMD_SHIFT)
| ^~~~~~~~~~~~
Exposed by commit
9b89a073e1ca ("ARM: 9149/1: add BUILD_BUG_ON to check if fixmap range spans multiple pmds")
I have no idea why that BUILD_BUG_ON hits, so I have just reverted that
commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-10-25 23:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 23:25 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-03 0:15 linux-next: build failure after merge of the arm tree Stephen Rothwell
2024-05-03 8:18 ` Russell King (Oracle)
2024-05-03 8:23 ` Russell King (Oracle)
2024-05-03 12:08 ` Stephen Rothwell
2024-05-03 12:29 ` Russell King (Oracle)
2022-08-31 9:10 Stephen Rothwell
2022-08-31 9:14 ` Matija Glavinic Pecotic
2020-01-19 21:24 Stephen Rothwell
2020-01-19 21:31 ` Stephen Rothwell
2020-01-19 22:02 ` Russell King - ARM Linux admin
2017-04-20 22:40 Stephen Rothwell
2017-04-21 7:58 ` Mason
2017-04-21 8:12 ` Stephen Rothwell
2017-04-21 8:30 ` Mason
2017-04-21 23:43 ` Russell King - ARM Linux
2017-04-22 8:41 ` Mason
2017-04-24 4:20 ` Vinod Koul
2017-06-14 19:23 ` Mason
2017-04-21 11:27 ` Mason
2015-05-29 1:09 Stephen Rothwell
2014-04-10 1:35 Stephen Rothwell
2011-03-02 14:13 Stephen Rothwell
2011-03-02 15:55 ` Nicolas Pitre
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=20211026102536.31e5ab62@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=quanyang.wang@windriver.com \
/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;
as well as URLs for NNTP newsgroup(s).