From: Ben Horgan <ben.horgan@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Yury Norov <yury.norov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the bitmap tree
Date: Thu, 10 Jul 2025 09:44:09 +0100 [thread overview]
Message-ID: <c8c94357-8367-42b9-a817-f4ae3feacdf2@arm.com> (raw)
In-Reply-To: <20250710183449.20e255b4@canb.auug.org.au>
Hi Stephen,
On 7/10/25 09:34, Stephen Rothwell wrote:
> Hi all,
>
> After merging the bitmap tree, today's linux-next build (arm64 defconfig)
> produced this warning:
>
> arch/arm64/kvm/sys_regs.c: In function 'access_mdcr':
> arch/arm64/kvm/sys_regs.c:2654:17: warning: ignoring return value of 'u64_replace_bits' declared with attribute 'warn_unused_result' [-Wunused-result]
> 2654 | u64_replace_bits(val, hpmn, MDCR_EL2_HPMN);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Introduced by commit
>
> f66f9c3d09c1 ("bitfield: Ensure the return values of helper functions are checked")
>
Sorry to have broken your tree. However, this is a valid warning and
this misuse of u64_replace_bits() was the motivation for the commit.
The fix can be found here
https://lore.kernel.org/kvmarm/20250709093808.920284-1-ben.horgan@arm.com/T/#mc9e47859302654d84b4f2b3d9032d2b595d5df49
Thanks,
Ben
next prev parent reply other threads:[~2025-07-10 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 8:34 linux-next: build warning after merge of the bitmap tree Stephen Rothwell
2025-07-10 8:44 ` Ben Horgan [this message]
2025-07-10 12:00 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2022-07-15 12:22 Stephen Rothwell
2022-07-15 13:40 ` Yury Norov
2022-04-20 7:55 Stephen Rothwell
2022-04-20 8:29 ` Yury Norov
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=c8c94357-8367-42b9-a817-f4ae3feacdf2@arm.com \
--to=ben.horgan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=yury.norov@gmail.com \
/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