From: kernel test robot <lkp@intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-renesas-soc@vger.kernel.org
Subject: [geert-renesas-drivers:topic/rcar-v4h-pinctrl-fixes-v1] BUILD SUCCESS 64999caeaefdd1b34d2618c61fabc8d3c826ef5c
Date: Sun, 30 Jun 2024 00:43:43 +0800 [thread overview]
Message-ID: <202406300041.SlWhPoRg-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git topic/rcar-v4h-pinctrl-fixes-v1
branch HEAD: 64999caeaefdd1b34d2618c61fabc8d3c826ef5c pinctrl: renesas: r8a779g0: Add INTC-EX pins, groups, and function
elapsed time: 6009m
configs tested: 66
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha defconfig gcc-13.2.0
arc defconfig gcc-13.2.0
arc randconfig-001-20240627 gcc-13.2.0
arc randconfig-002-20240627 gcc-13.2.0
arm collie_defconfig gcc-13.2.0
arm davinci_all_defconfig clang-19
arm defconfig clang-14
arm h3600_defconfig gcc-13.2.0
arm integrator_defconfig clang-19
arm ixp4xx_defconfig gcc-13.2.0
arm randconfig-001-20240627 gcc-13.2.0
arm randconfig-002-20240627 clang-19
arm randconfig-003-20240627 gcc-13.2.0
arm randconfig-004-20240627 clang-19
arm vt8500_v6_v7_defconfig gcc-13.2.0
arm64 defconfig gcc-13.2.0
arm64 randconfig-001-20240627 gcc-13.2.0
arm64 randconfig-002-20240627 clang-19
arm64 randconfig-003-20240627 clang-17
arm64 randconfig-004-20240627 clang-19
csky defconfig gcc-13.2.0
csky randconfig-001-20240627 gcc-13.2.0
csky randconfig-002-20240627 gcc-13.2.0
hexagon defconfig clang-19
hexagon randconfig-001-20240627 clang-17
hexagon randconfig-002-20240627 clang-19
loongarch defconfig gcc-13.2.0
loongarch loongson3_defconfig gcc-13.2.0
loongarch randconfig-001-20240627 gcc-13.2.0
loongarch randconfig-002-20240627 gcc-13.2.0
m68k defconfig gcc-13.2.0
m68k m5272c3_defconfig gcc-13.2.0
m68k m5275evb_defconfig gcc-13.2.0
m68k multi_defconfig gcc-13.2.0
microblaze defconfig gcc-13.2.0
nios2 defconfig gcc-13.2.0
nios2 randconfig-001-20240627 gcc-13.2.0
nios2 randconfig-002-20240627 gcc-13.2.0
parisc randconfig-001-20240627 gcc-13.2.0
parisc randconfig-002-20240627 gcc-13.2.0
parisc64 defconfig gcc-13.2.0
powerpc acadia_defconfig clang-19
powerpc eiger_defconfig clang-19
powerpc mpc866_ads_defconfig clang-19
powerpc randconfig-001-20240627 gcc-13.2.0
powerpc randconfig-002-20240627 clang-19
powerpc randconfig-003-20240627 gcc-13.2.0
powerpc tqm8555_defconfig clang-19
powerpc64 randconfig-001-20240627 gcc-13.2.0
powerpc64 randconfig-002-20240627 gcc-13.2.0
powerpc64 randconfig-003-20240627 gcc-13.2.0
riscv randconfig-001-20240627 gcc-13.2.0
riscv randconfig-002-20240627 clang-19
s390 randconfig-001-20240627 clang-16
s390 randconfig-002-20240627 clang-15
sh ecovec24-romimage_defconfig gcc-13.2.0
sh randconfig-001-20240627 gcc-13.2.0
sh randconfig-002-20240627 gcc-13.2.0
sh rts7751r2d1_defconfig gcc-13.2.0
sh se7721_defconfig gcc-13.2.0
sparc64 randconfig-001-20240627 gcc-13.2.0
sparc64 randconfig-002-20240627 gcc-13.2.0
um randconfig-001-20240627 clang-19
um randconfig-002-20240627 clang-19
xtensa randconfig-001-20240627 gcc-13.2.0
xtensa randconfig-002-20240627 gcc-13.2.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-29 16:43 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=202406300041.SlWhPoRg-lkp@intel.com \
--to=lkp@intel.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.