From: Sasha Levin <sashal@kernel.org>
To: kernelci-results@groups.io
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, KernelCI bot <bot@kernelci.org>
Subject: Re: [REGRESSION] stable-rc/linux-5.15.y: (build) mixing declarations and code is a C99 extension [-Werror,-Wdeclara...
Date: Wed, 22 Jul 2026 12:43:15 -0400 [thread overview]
Message-ID: <20260722113505.rc-reply-0005@kernel.org> (raw)
In-Reply-To: <178467474395.1334.6033734617150761914@kernelci.org>
On Tue, Jul 21, 2026 at 10:59:04PM -0000, KernelCI bot wrote:
> New build issue found on stable-rc/linux-5.15.y:
>
> /tmp/kci/linux/arch/arm64/kvm/vgic/vgic-its.c:716:2: error: mixing declarations and code is a C99 extension [-Werror,-Wdeclaration-after-statement]
> 716 | guard(srcu)(&kvm->srcu);
The 5.15 backport of 3a0724998162 ("KVM: Move kvm_io_bus_get_dev()
locking responsibilities to callers") placed guard(srcu) after a
statement, which 5.15.y still rejects with
-Wdeclaration-after-statement.
Fixed by replacing the 5.15 backport with the 5.10 backport of the
same upstream commit, which uses explicit
srcu_read_lock()/srcu_read_unlock() instead of guard() - the affected
functions are identical between the two trees. The next -rc should
build cleanly.
Thanks for the report.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-07-22 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 22:59 [REGRESSION] stable-rc/linux-5.15.y: (build) mixing declarations and code is a C99 extension [-Werror,-Wdeclara KernelCI bot
2026-07-22 16:43 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-20 12:59 KernelCI bot
2026-05-30 12:59 KernelCI bot
2026-05-30 15:48 ` Sasha Levin
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=20260722113505.rc-reply-0005@kernel.org \
--to=sashal@kernel.org \
--cc=bot@kernelci.org \
--cc=kernelci-results@groups.io \
--cc=stable@vger.kernel.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