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-v6.19] BUILD SUCCESS 9d22a34a016313137b9e534a918f1f9aa790aa69
Date: Sat, 01 Nov 2025 18:14:07 +0800 [thread overview]
Message-ID: <202511011801.OqFa5HMh-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git renesas-dts-for-v6.19
branch HEAD: 9d22a34a016313137b9e534a918f1f9aa790aa69 arm64: dts: renesas: sparrow-hawk: Fix full-size DP connector node name and labels
elapsed time: 1475m
configs tested: 23
configs skipped: 158
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
arm allnoconfig clang-22
arm mvebu_v7_defconfig clang-22
arm randconfig-001-20251031 gcc-14.3.0
arm randconfig-002-20251031 clang-22
arm randconfig-003-20251031 gcc-11.5.0
arm randconfig-004-20251031 clang-22
arm spear3xx_defconfig clang-17
arm spear6xx_defconfig clang-22
arm vexpress_defconfig gcc-15.1.0
arm64 allnoconfig gcc-15.1.0
arm64 allyesconfig clang-22
hexagon randconfig-001-20251101 clang-19
hexagon randconfig-002-20251101 clang-19
loongarch randconfig-001-20251101 clang-19
loongarch randconfig-002-20251101 clang-19
nios2 randconfig-001-20251101 clang-19
nios2 randconfig-002-20251101 clang-19
parisc randconfig-001-20251101 clang-20
parisc randconfig-002-20251101 clang-20
powerpc randconfig-001-20251101 clang-20
powerpc randconfig-002-20251101 clang-20
powerpc64 randconfig-001-20251101 clang-20
powerpc64 randconfig-002-20251101 clang-20
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-01 10:14 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=202511011801.OqFa5HMh-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.