From: Bjorn Helgaas <helgaas@kernel.org>
To: kernelci@lists.linux.dev
Cc: kernelci-results@groups.io, gus@collabora.com, linux-pci@vger.kernel.org
Subject: Re: [REGRESSION] linux-pci/next: (build) ignoring return value of ‘vga_get_uninterruptible’ declared with a...
Date: Mon, 30 Mar 2026 12:14:33 -0500 [thread overview]
Message-ID: <20260330171433.GA84073@bhelgaas> (raw)
In-Reply-To: <177463434509.1554.4896275539353552635@0d12152ffbcd>
On Fri, Mar 27, 2026 at 05:59:05PM -0000, KernelCI bot wrote:
>
>
>
>
> Hello,
>
> New build issue found on linux-pci/next:
>
> ---
> ignoring return value of ‘vga_get_uninterruptible’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result] in drivers/gpu/drm/i915/display/intel_vga.o (drivers/gpu/drm/i915/display/intel_vga.c) [logspec:kbuild,kbuild.compiler.error]
> ---
>
> - dashboard: https://d.kernelci.org/i/maestro:f670fdf443306495220d2cea8670ce85a80aed1e
> - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git
> - commit HEAD: 50451816531d66141cafe2347f9a896bd4dcb2b3
Dropped the commits related to this, see
https://lore.kernel.org/all/20260330161802.GA79047@bhelgaas
>
>
> Please include the KernelCI tag when submitting a fix:
>
> Reported-by: kernelci.org bot <bot@kernelci.org>
>
>
> Log excerpt:
> =====================================================
> /tmp/kci/linux/drivers/gpu/drm/i915/display/intel_vga.c:68:9: error: ignoring return value of ‘vga_get_uninterruptible’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
> 68 | vga_get_uninterruptible(pdev, VGA_RSRC_LEGACY_IO);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> /tmp/kci/linux/drivers/gpu/drm/i915/display/intel_vga.c: In function ‘intel_vga_reset_io_mem’:
> /tmp/kci/linux/drivers/gpu/drm/i915/display/intel_vga.c:93:9: error: ignoring return value of ‘vga_get_uninterruptible’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
> 93 | vga_get_uninterruptible(pdev, VGA_RSRC_LEGACY_IO);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
>
> =====================================================
>
>
> # Builds where the incident occurred:
>
> ## x86_64_defconfig+kselftest on (x86_64):
> - compiler: gcc-14
> - config: None
> - dashboard: https://d.kernelci.org/build/maestro:69c6b9023712df3240c2a985
>
>
> #kernelci issue maestro:f670fdf443306495220d2cea8670ce85a80aed1e
>
> --
> This is an experimental report format. Please send feedback in!
> Talk to us at kernelci@lists.linux.dev
>
> Made with love by the KernelCI team - https://kernelci.org
parent reply other threads:[~2026-03-30 17:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <177463434509.1554.4896275539353552635@0d12152ffbcd>]
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=20260330171433.GA84073@bhelgaas \
--to=helgaas@kernel.org \
--cc=gus@collabora.com \
--cc=kernelci-results@groups.io \
--cc=kernelci@lists.linux.dev \
--cc=linux-pci@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