Linux-Next discussions
 help / color / mirror / Atom feed
From: KernelCI bot <bot@kernelci.org>
To: kernelci-results@groups.io
Cc: regressions@lists.linux.dev, linux-next@vger.kernel.org
Subject: [REGRESSION] next/master: (build)‘parse_edid_cea’ defined but not used [-Werror=unused-function] in ...
Date: Fri, 11 Sep 2026 16:59:07 -0000	[thread overview]
Message-ID: <178914594745.4423.13336797159691042320@kernelci.org> (raw)

New build issue found on next/master:

---
‘parse_edid_cea’ defined but not used [-Werror=unused-function] in drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_connector.o (drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_connector.c) [logspec:kbuild,kbuild.compiler.error]
---

Log excerpt:
=====================================================
/tmp/kci/linux/drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_connector.c:3690:23: error: ‘parse_edid_cea’ defined but not used [-Werror=unused-function]
 3690 | STATIC_IFN_KUNIT bool parse_edid_cea(struct amdgpu_dm_connector *aconnector,
      |                       ^~~~~~~~~~~~~~
cc1: all warnings being treated as errors

=====================================================

When fixing this issue, please attribute this report according to the
patch submission rules:

Reported-by: kernelci.org bot <bot@kernelci.org>
Link: https://lore.kernel.org/all/178914594745.4423.13336797159691042320@kernelci.org/

For complete logs and details about the environment used, see the issue
on the KernelCI dashboard:

- dashboard: https://d.kernelci.org/i/maestro:062b6b4e2382aba3e97943acd24e9dea1debfc26
- giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
- commit HEAD:  68142f986ff04b2b70b31db00f719bf690f64a9a
- tags: next-20260911

# Builds where the incident occurred:

## x86_64_defconfig+kcidebug+kcidebug-x86_64+x86-board on (x86_64):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6aa4280120239ade90233200

## x86_64_defconfig+lab-setup+x86-board+kselftest on (x86_64):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6aa427ec20239ade902331e9

## x86_64_defconfig+lab-setup+x86-board+kselftest on (x86_64):
- compiler: gcc-15
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6aa427f020239ade902331ed

#regzbot introduced: f2bfbc3554ca6919484030729424b9dee2942d24..68142f986ff04b2b70b31db00f719bf690f64a9a
#regzbot link: https://d.kernelci.org/i/maestro:062b6b4e2382aba3e97943acd24e9dea1debfc26

#kernelci issue maestro:062b6b4e2382aba3e97943acd24e9dea1debfc26

--
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-09-11 16:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178914594745.4423.13336797159691042320@kernelci.org \
    --to=bot@kernelci.org \
    --cc=kernelci-results@groups.io \
    --cc=kernelci@lists.linux.dev \
    --cc=linux-next@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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