From: bugzilla-daemon@kernel•org
To: linuxppc-dev@lists•ozlabs.org
Subject: [Bug 215567] New: build failure when PPC_64S_HASH_MMU=n is selected in kernel .config
Date: Fri, 04 Feb 2022 13:00:35 +0000 [thread overview]
Message-ID: <bug-215567-206035@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215567
Bug ID: 215567
Summary: build failure when PPC_64S_HASH_MMU=n is selected in
kernel .config
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: 5.17-rc2
Hardware: PPC-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: PPC-64
Assignee: platform_ppc-64@kernel-bugs•osdl.org
Reporter: erhard_f@mailbox•org
Regression: No
Created attachment 300391
--> https://bugzilla.kernel.org/attachment.cgi?id=300391&action=edit
kernel .config (kernel 5.17-rc2, Talos II)
[...]
CC arch/powerpc/kernel/stacktrace.o
CC arch/powerpc/kernel/setup_64.o
arch/powerpc/kernel/setup_64.c: In function 'setup_per_cpu_areas':
arch/powerpc/kernel/setup_64.c:811:21: error: 'mmu_linear_psize' undeclared
(first use in this function); did you mean 'mmu_virtual_psize'?
811 | if (mmu_linear_psize == MMU_PAGE_4K)
| ^~~~~~~~~~~~~~~~
| mmu_virtual_psize
arch/powerpc/kernel/setup_64.c:811:21: note: each undeclared identifier is
reported only once for each function it appears in
make[2]: *** [scripts/Makefile.build:288: arch/powerpc/kernel/setup_64.o]
Fehler 1
Got this with PPC_64S_HASH_MMU=n on my Talos II. When PPC_64S_HASH_MMU is
enabled the kernel builds ok.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-02-04 13:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 13:00 bugzilla-daemon [this message]
2022-03-01 17:20 ` [Bug 215567] build failure when PPC_64S_HASH_MMU=n is selected in kernel .config bugzilla-daemon
2022-03-01 18:42 ` bugzilla-daemon
2022-03-01 19:57 ` bugzilla-daemon
2022-03-01 20:52 ` bugzilla-daemon
2022-03-01 22:30 ` bugzilla-daemon
2022-03-12 13:22 ` bugzilla-daemon
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=bug-215567-206035@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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