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:renesas-clk-for-v6.20] BUILD SUCCESS 3099b7d2d7ecae523036abe0cabfae25e8e56349
Date: Sun, 30 Nov 2025 20:37:19 +0800 [thread overview]
Message-ID: <202511302013.8P7N1wMX-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git renesas-clk-for-v6.20
branch HEAD: 3099b7d2d7ecae523036abe0cabfae25e8e56349 clk: renesas: r9a09g056: Add entries for the RSPIs
elapsed time: 2884m
configs tested: 72
configs skipped: 1
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc-15.1.0
alpha defconfig gcc-15.1.0
arc allnoconfig gcc-15.1.0
arc defconfig gcc-15.1.0
arc hsdk_defconfig gcc-15.1.0
arc randconfig-001-20251129 gcc-8.5.0
arc randconfig-002-20251129 gcc-8.5.0
arm allnoconfig clang-22
arm defconfig clang-22
arm lpc18xx_defconfig clang-22
arm netwinder_defconfig gcc-15.1.0
arm randconfig-001-20251129 clang-20
arm randconfig-002-20251129 gcc-10.5.0
arm randconfig-003-20251129 gcc-13.4.0
arm randconfig-004-20251129 gcc-8.5.0
arm spear3xx_defconfig clang-17
arm64 allnoconfig gcc-15.1.0
arm64 defconfig gcc-15.1.0
arm64 randconfig-003-20251129 gcc-8.5.0
csky allmodconfig gcc-15.1.0
csky allnoconfig gcc-15.1.0
csky defconfig gcc-15.1.0
csky randconfig-001-20251129 gcc-15.1.0
hexagon allnoconfig clang-22
hexagon defconfig clang-22
hexagon randconfig-001-20251129 clang-22
hexagon randconfig-002-20251129 clang-22
i386 allnoconfig gcc-14
i386 buildonly-randconfig-001-20251129 clang-20
i386 buildonly-randconfig-002-20251129 clang-20
i386 buildonly-randconfig-003-20251129 gcc-14
i386 buildonly-randconfig-004-20251129 gcc-12
i386 defconfig clang-20
i386 randconfig-011-20251129 clang-20
i386 randconfig-012-20251129 gcc-13
i386 randconfig-013-20251129 clang-20
i386 randconfig-014-20251129 clang-20
i386 randconfig-015-20251129 gcc-14
i386 randconfig-016-20251129 clang-20
i386 randconfig-017-20251129 gcc-14
loongarch allnoconfig clang-22
loongarch randconfig-001-20251129 gcc-15.1.0
loongarch randconfig-002-20251129 gcc-14.3.0
m68k allnoconfig gcc-15.1.0
microblaze allnoconfig gcc-15.1.0
microblaze defconfig gcc-15.1.0
mips allmodconfig gcc-15.1.0
mips allnoconfig gcc-15.1.0
mips allyesconfig gcc-15.1.0
nios2 allnoconfig gcc-11.5.0
nios2 defconfig gcc-11.5.0
nios2 randconfig-001-20251129 gcc-11.5.0
nios2 randconfig-002-20251129 gcc-11.5.0
openrisc allnoconfig gcc-15.1.0
openrisc defconfig gcc-15.1.0
parisc allnoconfig gcc-15.1.0
parisc randconfig-001-20251129 gcc-10.5.0
parisc randconfig-002-20251129 gcc-13.4.0
powerpc allnoconfig gcc-15.1.0
powerpc randconfig-001-20251129 gcc-8.5.0
powerpc randconfig-002-20251129 clang-22
powerpc64 randconfig-001-20251129 gcc-8.5.0
powerpc64 randconfig-002-20251129 gcc-13.4.0
riscv allnoconfig gcc-15.1.0
s390 allnoconfig clang-22
sh allmodconfig gcc-15.1.0
sh allnoconfig gcc-15.1.0
sh allyesconfig gcc-15.1.0
sparc allnoconfig gcc-15.1.0
um allnoconfig clang-22
x86_64 allnoconfig clang-20
xtensa allnoconfig gcc-15.1.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-30 12: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=202511302013.8P7N1wMX-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 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).