From: Wentao Guan <guanwentao@uniontech.com>
To: gregkh@linuxfoundation.org
Cc: achill@achill.org, akpm@linux-foundation.org, broonie@kernel.org,
conor@kernel.org, f.fainelli@gmail.com, hargar@microsoft.com,
jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
linux@roeck-us.net, lkft-triage@lists.linaro.org,
patches@kernelci.org, patches@lists.linux.dev,
pavel@nabladev.com, rwarsow@gmx.de, shuah@kernel.org,
sr@sladewatkins.com, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org,
Wentao Guan <guanwentao@uniontech.com>
Subject: Re: [PATCH 6.18 000/621] 6.18.57-rc1 review
Date: Wed, 14 Oct 2026 13:43:55 +0800 [thread overview]
Message-ID: <20261014054354.4048552-1-guanwentao@uniontech.com> (raw)
In-Reply-To: <20261013112920.855194808@linuxfoundation.org>
Build tested in our x86,arm64,loongarch config successfully without error.
Tested-by: Wentao Guan <guanwentao@uniontech.com>
I met the same riscv 'RISCV_ISA_EXT_H' build issue others had reported.
Best Regards
Wentao Guan
Log:
arch/riscv/kernel/cpufeature.c: In function ‘riscv_clear_hypervisor_csr’:
arch/riscv/kernel/cpufeature.c:1140:43: error: ‘RISCV_ISA_EXT_H’ undeclared (first use in this function); did you mean ‘RISCV_ISA_EXT_h’?
1140 | if (!riscv_has_extension_unlikely(RISCV_ISA_EXT_H))
| ^~~~~~~~~~~~~~~
| RISCV_ISA_EXT_h
arch/riscv/kernel/cpufeature.c:1140:43: note: each undeclared identifier is reported only once for each function it appears in
CC arch/riscv/kernel/acpi.o
CC arch/riscv/kernel/pi/cmdline_early.o
CC arch/riscv/kernel/acpi_numa.o
prev parent reply other threads:[~2026-10-14 5:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 11:29 Greg Kroah-Hartman
2026-10-13 12:29 ` Brett A C Sheffield
2026-10-13 13:13 ` Pavel Machek
2026-10-13 19:19 ` Florian Fainelli
2026-10-13 20:20 ` Peter Schneider
2026-10-14 1:27 ` Sasha Levin
2026-10-14 8:36 ` Brett A C Sheffield
2026-10-14 9:01 ` Greg Kroah-Hartman
2026-10-13 17:07 ` Miguel Ojeda
2026-10-13 23:11 ` Shuah Khan
2026-10-14 5:43 ` Wentao Guan [this message]
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=20261014054354.4048552-1-guanwentao@uniontech.com \
--to=guanwentao@uniontech.com \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®