From: kernel test robot <lkp@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org
Subject: [linusw-pinctrl:devel] BUILD REGRESSION da53dcd54cc35efa7a8236846bb39d40deeee034
Date: Sun, 23 Nov 2025 03:36:58 +0800 [thread overview]
Message-ID: <202511230352.zZGPjqki-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel
branch HEAD: da53dcd54cc35efa7a8236846bb39d40deeee034 dt-bindings: pinctrl: cix,sky1-pinctrl: Drop duplicate newline
Error/Warning (recently discovered and may have been fixed):
include/linux/pinctrl/pinconf-generic.h:235:(.ltext+0x299): undefined reference to `pinconf_generic_dt_node_to_map'
Error/Warning ids grouped by kconfigs:
recent_errors
`-- um-randconfig-r121-20251121
`-- include-linux-pinctrl-pinconf-generic.h:(.ltext):undefined-reference-to-pinconf_generic_dt_node_to_map
elapsed time: 1571m
configs tested: 58
configs skipped: 0
tested configs:
alpha allnoconfig gcc-15.1.0
arc allnoconfig gcc-15.1.0
arc randconfig-001-20251122 gcc-14.3.0
arc randconfig-002-20251122 gcc-9.5.0
arm allnoconfig clang-22
arm randconfig-001-20251122 clang-22
arm randconfig-002-20251122 clang-22
arm randconfig-003-20251122 clang-22
arm randconfig-004-20251122 gcc-12.5.0
arm64 allnoconfig gcc-15.1.0
arm64 randconfig-001-20251122 gcc-8.5.0
arm64 randconfig-002-20251122 gcc-9.5.0
arm64 randconfig-003-20251122 gcc-10.5.0
arm64 randconfig-004-20251122 clang-22
csky allnoconfig gcc-15.1.0
csky randconfig-001-20251122 gcc-15.1.0
csky randconfig-002-20251122 gcc-14.3.0
hexagon allnoconfig clang-22
hexagon randconfig-001-20251122 clang-22
hexagon randconfig-002-20251122 clang-17
i386 allnoconfig gcc-14
loongarch allnoconfig clang-22
loongarch randconfig-001-20251122 gcc-12.5.0
loongarch randconfig-002-20251122 gcc-14.3.0
m68k allnoconfig gcc-15.1.0
microblaze allnoconfig gcc-15.1.0
mips allnoconfig gcc-15.1.0
nios2 allnoconfig gcc-11.5.0
nios2 randconfig-001-20251122 gcc-11.5.0
nios2 randconfig-002-20251122 gcc-8.5.0
openrisc allnoconfig gcc-15.1.0
parisc allnoconfig gcc-15.1.0
parisc randconfig-001-20251123 gcc-14.3.0
parisc randconfig-002-20251123 gcc-14.3.0
powerpc allnoconfig gcc-15.1.0
powerpc randconfig-001-20251123 clang-22
powerpc randconfig-002-20251123 gcc-8.5.0
riscv allnoconfig gcc-15.1.0
riscv randconfig-001-20251122 clang-22
riscv randconfig-002-20251122 clang-22
s390 allnoconfig clang-22
s390 randconfig-001-20251122 clang-16
s390 randconfig-002-20251122 gcc-13.4.0
sh allnoconfig gcc-15.1.0
sh randconfig-001-20251122 gcc-15.1.0
sh randconfig-002-20251122 gcc-10.5.0
sparc allnoconfig gcc-15.1.0
sparc randconfig-001-20251122 gcc-13.4.0
sparc randconfig-002-20251122 gcc-11.5.0
sparc64 randconfig-001-20251122 gcc-13.4.0
sparc64 randconfig-002-20251122 clang-22
um allnoconfig clang-22
um randconfig-001-20251122 clang-22
um randconfig-002-20251122 clang-22
x86_64 allnoconfig clang-20
xtensa allnoconfig gcc-15.1.0
xtensa randconfig-001-20251122 gcc-12.5.0
xtensa randconfig-002-20251122 gcc-8.5.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-22 19:37 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=202511230352.zZGPjqki-lkp@intel.com \
--to=lkp@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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;
as well as URLs for NNTP newsgroup(s).