public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Yury Norov <yury.norov@gmail.com>
Cc: Ben Horgan <ben.horgan@arm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the bitmap tree
Date: Thu, 10 Jul 2025 18:34:49 +1000	[thread overview]
Message-ID: <20250710183449.20e255b4@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 603 bytes --]

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")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2025-07-10  8:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10  8:34 Stephen Rothwell [this message]
2025-07-10  8:44 ` linux-next: build warning after merge of the bitmap tree Ben Horgan
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=20250710183449.20e255b4@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ben.horgan@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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