From: kernel test robot <lkp@intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-renesas-soc@vger.kernel.org
Subject: [geert-renesas-devel:renesas-dts-for-v7.1] BUILD SUCCESS cf3a5a77d82cec9f48b4bcb615876d020566e43a
Date: Sat, 21 Mar 2026 12:27:25 +0800 [thread overview]
Message-ID: <202603211218.eRomnKAn-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git renesas-dts-for-v7.1
branch HEAD: cf3a5a77d82cec9f48b4bcb615876d020566e43a arm64: dts: renesas: rzt2h-rzn2h-evk: Fix GMAC pins sort order
elapsed time: 787m
configs tested: 32
configs skipped: 140
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc-15.2.0
arc allnoconfig gcc-15.2.0
arm allnoconfig clang-23
arm allnoconfig gcc-15.2.0
arm allyesconfig gcc-15.2.0
arm h3600_defconfig gcc-15.2.0
arm64 allmodconfig clang-19
arm64 allnoconfig gcc-15.2.0
csky allnoconfig gcc-15.2.0
hexagon allnoconfig gcc-15.2.0
i386 allnoconfig gcc-15.2.0
loongarch allnoconfig gcc-15.2.0
m68k allnoconfig gcc-15.2.0
microblaze allnoconfig gcc-15.2.0
mips allnoconfig gcc-15.2.0
nios2 allnoconfig clang-23
openrisc allnoconfig clang-23
parisc allnoconfig clang-23
powerpc allnoconfig clang-23
riscv allnoconfig clang-23
s390 allnoconfig clang-23
sh allnoconfig clang-23
sh defconfig gcc-14
sparc allnoconfig clang-23
sparc64 defconfig gcc-14
um allnoconfig clang-23
um defconfig gcc-14
um i386_defconfig gcc-14
um x86_64_defconfig gcc-14
x86_64 allnoconfig clang-23
x86_64 defconfig gcc-14
xtensa allnoconfig clang-23
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-21 4:27 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=202603211218.eRomnKAn-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