From: kernel test robot <lkp@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-acpi@vger.kernel.org, devel@acpica.org, linux-pm@vger.kernel.org
Subject: [rafael-pm:bleeding-edge] BUILD REGRESSION c7d553cb161f03e4424c88bddc26fadcbbf4b6d5
Date: Sun, 13 Oct 2024 20:31:08 +0800 [thread overview]
Message-ID: <202410132058.VIShcV1a-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
branch HEAD: c7d553cb161f03e4424c88bddc26fadcbbf4b6d5 Merge branch 'thermal-core-experimental' into bleeding-edge
Error/Warning (recently discovered and may have been fixed):
https://lore.kernel.org/oe-kbuild-all/202410131909.OG5cXVR5-lkp@intel.com
drivers/thermal/thermal_sysfs.c:726:17: error: label 'unlock' used but not defined
Error/Warning ids grouped by kconfigs:
recent_errors
`-- i386-buildonly-randconfig-002-20241013
`-- drivers-thermal-thermal_sysfs.c:error:label-unlock-used-but-not-defined
elapsed time: 2435m
configs tested: 22
configs skipped: 0
tested configs:
i386 buildonly-randconfig-001-20241013 clang-18
i386 buildonly-randconfig-002-20241013 gcc-12
i386 buildonly-randconfig-003-20241013 clang-18
i386 buildonly-randconfig-004-20241013 gcc-12
i386 buildonly-randconfig-005-20241013 clang-18
i386 buildonly-randconfig-006-20241013 clang-18
i386 randconfig-001-20241013 clang-18
i386 randconfig-002-20241013 gcc-12
i386 randconfig-003-20241013 gcc-12
i386 randconfig-004-20241013 gcc-11
i386 randconfig-005-20241013 clang-18
i386 randconfig-006-20241013 clang-18
i386 randconfig-011-20241013 clang-18
i386 randconfig-012-20241013 gcc-12
openrisc allnoconfig gcc-14.1.0
parisc allnoconfig gcc-14.1.0
powerpc allnoconfig gcc-14.1.0
riscv allnoconfig gcc-14.1.0
s390 allnoconfig clang-20
um allnoconfig clang-17
x86_64 kexec clang-18
x86_64 rhel-8.3 gcc-12
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-10-13 12:31 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=202410132058.VIShcV1a-lkp@intel.com \
--to=lkp@intel.com \
--cc=devel@acpica.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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