From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Huacai Chen <chenhuacai@loongson•cn>
Cc: Huacai Chen <chenhuacai@kernel•org>,
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 loongarch tree
Date: Mon, 8 Aug 2022 09:03:29 +1000 [thread overview]
Message-ID: <20220808090329.4763fe7b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 3956 bytes --]
Hi all,
After merging the loongarch tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/acpi/tables.c: In function 'acpi_table_print_madt_entry':
drivers/acpi/tables.c:213:14: error: 'ACPI_MADT_TYPE_CORE_PIC' undeclared (first use in this function); did you mean 'ACPI_MADT_TYPE_IO_SAPIC'?
213 | case ACPI_MADT_TYPE_CORE_PIC:
| ^~~~~~~~~~~~~~~~~~~~~~~
| ACPI_MADT_TYPE_IO_SAPIC
drivers/acpi/tables.c:213:14: note: each undeclared identifier is reported only once for each function it appears in
In file included from include/linux/printk.h:573,
from include/linux/kernel.h:29,
from drivers/acpi/tables.c:13:
drivers/acpi/tables.c:218:35: error: invalid use of undefined type 'struct acpi_madt_core_pic'
218 | p->processor_id, p->core_id,
| ^~
include/linux/dynamic_debug.h:134:29: note: in definition of macro '__dynamic_func_call'
134 | func(&id, ##__VA_ARGS__); \
| ^~~~~~~~~~~
include/linux/dynamic_debug.h:162:9: note: in expansion of macro '_dynamic_func_call'
162 | _dynamic_func_call(fmt, __dynamic_pr_debug, \
| ^~~~~~~~~~~~~~~~~~
include/linux/printk.h:588:9: note: in expansion of macro 'dynamic_pr_debug'
588 | dynamic_pr_debug(fmt, ##__VA_ARGS__)
| ^~~~~~~~~~~~~~~~
drivers/acpi/tables.c:217:25: note: in expansion of macro 'pr_debug'
217 | pr_debug("CORE PIC (processor_id[0x%02x] core_id[0x%02x] %s)\n",
| ^~~~~~~~
drivers/acpi/tables.c:218:52: error: invalid use of undefined type 'struct acpi_madt_core_pic'
218 | p->processor_id, p->core_id,
| ^~
include/linux/dynamic_debug.h:134:29: note: in definition of macro '__dynamic_func_call'
134 | func(&id, ##__VA_ARGS__); \
| ^~~~~~~~~~~
include/linux/dynamic_debug.h:162:9: note: in expansion of macro '_dynamic_func_call'
162 | _dynamic_func_call(fmt, __dynamic_pr_debug, \
| ^~~~~~~~~~~~~~~~~~
include/linux/printk.h:588:9: note: in expansion of macro 'dynamic_pr_debug'
588 | dynamic_pr_debug(fmt, ##__VA_ARGS__)
| ^~~~~~~~~~~~~~~~
drivers/acpi/tables.c:217:25: note: in expansion of macro 'pr_debug'
217 | pr_debug("CORE PIC (processor_id[0x%02x] core_id[0x%02x] %s)\n",
| ^~~~~~~~
drivers/acpi/tables.c:219:36: error: invalid use of undefined type 'struct acpi_madt_core_pic'
219 | (p->flags & ACPI_MADT_ENABLED) ? "enabled" : "disabled");
| ^~
include/linux/dynamic_debug.h:134:29: note: in definition of macro '__dynamic_func_call'
134 | func(&id, ##__VA_ARGS__); \
| ^~~~~~~~~~~
include/linux/dynamic_debug.h:162:9: note: in expansion of macro '_dynamic_func_call'
162 | _dynamic_func_call(fmt, __dynamic_pr_debug, \
| ^~~~~~~~~~~~~~~~~~
include/linux/printk.h:588:9: note: in expansion of macro 'dynamic_pr_debug'
588 | dynamic_pr_debug(fmt, ##__VA_ARGS__)
| ^~~~~~~~~~~~~~~~
drivers/acpi/tables.c:217:25: note: in expansion of macro 'pr_debug'
217 | pr_debug("CORE PIC (processor_id[0x%02x] core_id[0x%02x] %s)\n",
| ^~~~~~~~
Caused by commit
0541f3fad39f ("LoongArch: Parse MADT to get multi-processor information")
I have used the loongarch tree from next-20220805 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-08-07 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 23:03 Stephen Rothwell [this message]
2022-08-08 7:28 ` linux-next: build failure after merge of the loongarch tree Huacai Chen
-- strict thread matches above, loose matches on Subject: below --
2024-09-12 0:35 Stephen Rothwell
2024-09-12 3:33 ` lixianglai
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=20220808090329.4763fe7b@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=chenhuacai@kernel$(echo .)org \
--cc=chenhuacai@loongson$(echo .)cn \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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