linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 6156424a7d001cceeafe59b52209d6f36719b51d
Date: Thu, 27 Nov 2025 05:54:35 +0800	[thread overview]
Message-ID: <202511270529.a8fZlQyb-lkp@intel.com> (raw)

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel
branch HEAD: 6156424a7d001cceeafe59b52209d6f36719b51d  Merge tag 'intel-pinctrl-v6.19-1' of git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel into devel

Error/Warning (recently discovered and may have been fixed):

    pinctrl-pic64gx-gpio2.c:(.text+0xd0): undefined reference to `pinconf_generic_dt_node_to_map'

Error/Warning ids grouped by kconfigs:

recent_errors
`-- xtensa-randconfig-001-20251126
    `-- pinctrl-pic64gx-gpio2.c:(.text):undefined-reference-to-pinconf_generic_dt_node_to_map

elapsed time: 1489m

configs tested: 54
configs skipped: 0

tested configs:
alpha                   allnoconfig    gcc-15.1.0
arc                     allnoconfig    gcc-15.1.0
arc         randconfig-001-20251126    gcc-13.4.0
arc         randconfig-002-20251126    gcc-11.5.0
arm                     allnoconfig    clang-22
arm         randconfig-001-20251126    clang-22
arm         randconfig-002-20251126    clang-22
arm         randconfig-003-20251126    clang-19
arm         randconfig-004-20251126    clang-22
arm64                   allnoconfig    gcc-15.1.0
csky                    allnoconfig    gcc-15.1.0
hexagon                 allnoconfig    clang-22
hexagon     randconfig-001-20251126    clang-22
hexagon     randconfig-002-20251126    clang-22
i386                    allnoconfig    gcc-14
loongarch               allnoconfig    clang-22
loongarch   randconfig-001-20251126    gcc-15.1.0
loongarch   randconfig-002-20251126    clang-22
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-20251126    gcc-11.5.0
nios2       randconfig-002-20251126    gcc-9.5.0
openrisc                allnoconfig    gcc-15.1.0
parisc                  allnoconfig    gcc-15.1.0
parisc      randconfig-001-20251126    gcc-8.5.0
parisc      randconfig-002-20251126    gcc-15.1.0
powerpc                 allnoconfig    gcc-15.1.0
powerpc     randconfig-001-20251126    gcc-10.5.0
powerpc     randconfig-002-20251126    gcc-8.5.0
powerpc64   randconfig-001-20251126    clang-19
powerpc64   randconfig-002-20251126    clang-22
riscv                   allnoconfig    gcc-15.1.0
riscv       randconfig-001-20251126    gcc-10.5.0
riscv       randconfig-002-20251126    clang-22
s390                    allnoconfig    clang-22
s390        randconfig-001-20251126    gcc-8.5.0
s390        randconfig-002-20251126    gcc-8.5.0
sh                      allnoconfig    gcc-15.1.0
sh          randconfig-001-20251126    gcc-14.3.0
sh          randconfig-002-20251126    gcc-11.5.0
sparc                   allnoconfig    gcc-15.1.0
sparc       randconfig-001-20251126    gcc-8.5.0
sparc       randconfig-002-20251126    gcc-14.3.0
sparc64     randconfig-001-20251126    gcc-8.5.0
sparc64     randconfig-002-20251126    clang-22
um                      allnoconfig    clang-22
um          randconfig-001-20251126    clang-19
um          randconfig-002-20251126    clang-22
x86_64                  allnoconfig    clang-20
xtensa                  allnoconfig    gcc-15.1.0
xtensa      randconfig-001-20251126    gcc-14.3.0
xtensa      randconfig-002-20251126    gcc-10.5.0

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-11-26 21:55 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=202511270529.a8fZlQyb-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).