public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
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 function declared with 'warn_unused_resul...
Date: Mon, 30 Mar 2026 12:14:19 -0500	[thread overview]
Message-ID: <20260330171419.GA83942@bhelgaas> (raw)
In-Reply-To: <177463434349.1554.5266992356487229955@0d12152ffbcd>

On Fri, Mar 27, 2026 at 05:59:03PM -0000, KernelCI bot wrote:
> 
> 
> 
> 
> Hello,
> 
> New build issue found on linux-pci/next:
> 
> ---
>  ignoring return value of function declared with 'warn_unused_result' attribute [-Werror,-Wunused-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:c2145292d80ae85fd003068675e73a3d1f95c35e
> - 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:2: error: ignoring return value of function declared with 'warn_unused_result' attribute [-Werror,-Wunused-result]
>    68 |         vga_get_uninterruptible(pdev, VGA_RSRC_LEGACY_IO);
>       |         ^~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~
> /tmp/kci/linux/drivers/gpu/drm/i915/display/intel_vga.c:93:2: error: ignoring return value of function declared with 'warn_unused_result' attribute [-Werror,-Wunused-result]
>    93 |         vga_get_uninterruptible(pdev, VGA_RSRC_LEGACY_IO);
>       |         ^~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~
> 2 errors generated.
> 
> =====================================================
> 
> 
> # Builds where the incident occurred:
> 
> ## x86_64_defconfig on (x86_64):
> - compiler: clang-21
> - config: None
> - dashboard: https://d.kernelci.org/build/maestro:69c6b8d23712df3240c2a959
> 
> 
> #kernelci issue maestro:c2145292d80ae85fd003068675e73a3d1f95c35e
> 
> --
> 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

           reply	other threads:[~2026-03-30 17:14 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <177463434349.1554.5266992356487229955@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=20260330171419.GA83942@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