From: Jon Hunter <jonathanh@nvidia.com>
To: Pavel Machek <pavel@nabladev.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
f.fainelli@gmail.com, sudipm.mukherjee@gmail.com, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
achill@achill.org, sr@sladewatkins.com,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 6.18 000/315] 6.18.35-rc1 review
Date: Mon, 8 Jun 2026 13:13:50 +0100 [thread overview]
Message-ID: <c56becbe-aabe-4c27-9324-7119ccc68d6d@nvidia.com> (raw)
In-Reply-To: <aiWjTGe7fRnSvIl4@duo.ucw.cz>
On 07/06/2026 17:58, Pavel Machek wrote:
> Hi!
>
>> This is the start of the stable review cycle for the 6.18.35 release.
>> There are 315 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues with these being applied, please
>> let me know.
>
> We see build problem here:
>
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/14732223960
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/2582906697
>
> Best regards,
> Pavel
>
>
>
> arch/arm64/kvm/nested.c: In function 'kvm_init_nv_sysregs':
> 1807
> 12:45:08
> arch/arm64/kvm/nested.c:1776:9: error: 'resx' undeclared (first use in this function); did you mean 'res1'?
> 1808
> 12:45:08
> 1776 | resx.res0 = ZCR_ELx_RES0 | GENMASK_ULL(8, 4);
> 1809
> 12:45:08
> | ^~~~
> 1810
> 12:45:08
> | res1
> 1811
> 12:45:08
> arch/arm64/kvm/nested.c:1776:9: note: each undeclared identifier is reported only once for each function it appears in
> 1812
> 12:45:08
> arch/arm64/kvm/nested.c:1778:9: error: too few arguments to function 'set_sysreg_masks'
> 1813
> 12:45:08
> 1778 | set_sysreg_masks(kvm, ZCR_EL2, resx);
> 1814
> 12:45:08
> | ^~~~~~~~~~~~~~~~
> 1815
> 12:45:08
> arch/arm64/kvm/nested.c:1641:29: note: declared here
> 1816
> 12:45:08
> 1641 | static __always_inline void set_sysreg_masks(struct kvm *kvm, int sr, u64 res0, u64 res1)
> 1817
> 12:45:08
> | ^~~~~~~~~~~~~~~~
> 1818
> 12:45:08
> CC block/holder.o
> 1819
> 12:45:08
> CC drivers/irqchip/irq-ls-scfg-msi.o
> 1820
> 12:45:09
> make[4]: *** [scripts/Makefile.build:287: arch/arm64/kvm/nested.o]
> Error 1
I am seeing the same build error for ARM64.
Jon
--
nvpublic
next parent reply other threads:[~2026-06-08 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260607095727.528828913@linuxfoundation.org>
[not found] ` <aiWjTGe7fRnSvIl4@duo.ucw.cz>
2026-06-08 12:13 ` Jon Hunter [this message]
2026-06-08 13:30 ` [PATCH 6.18 000/315] 6.18.35-rc1 review Pavel Machek
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=c56becbe-aabe-4c27-9324-7119ccc68d6d@nvidia.com \
--to=jonathanh@nvidia.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=linux-kernel@vger.kernel.org \
--cc=linux-tegra@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