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-drivers-for-v6.2] BUILD SUCCESS 05b231db3c340b7a542f144158c4a5a97a90c02e
Date: Wed, 28 Sep 2022 03:49:14 +0800 [thread overview]
Message-ID: <633353ba.dWfgoGvhn3zWooiU%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git renesas-drivers-for-v6.2
branch HEAD: 05b231db3c340b7a542f144158c4a5a97a90c02e soc: renesas: Kconfig: Explicitly select GPIOLIB and PINCTRL config under SOC_RENESAS
elapsed time: 722m
configs tested: 104
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
um i386_defconfig
um x86_64_defconfig
powerpc allmodconfig
mips allyesconfig
powerpc allnoconfig
arc defconfig
s390 allmodconfig
alpha defconfig
s390 defconfig
sh allmodconfig
s390 allyesconfig
x86_64 defconfig
x86_64 rhel-8.3-func
x86_64 rhel-8.3-kselftests
arc allyesconfig
alpha allyesconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-syz
i386 defconfig
x86_64 rhel-8.3-kunit
m68k allmodconfig
arc randconfig-r043-20220925
x86_64 rhel-8.3-kvm
m68k allyesconfig
x86_64 allyesconfig
i386 randconfig-a001-20220926
arc randconfig-r043-20220926
s390 randconfig-r044-20220925
i386 randconfig-a004-20220926
i386 randconfig-a002-20220926
riscv randconfig-r042-20220925
i386 randconfig-a003-20220926
i386 randconfig-a005-20220926
i386 randconfig-a006-20220926
i386 allyesconfig
arm defconfig
x86_64 randconfig-a004
x86_64 randconfig-a002
x86_64 randconfig-a006
arm64 allyesconfig
arm allyesconfig
csky allnoconfig
alpha allnoconfig
arc allnoconfig
riscv allnoconfig
i386 randconfig-c001
i386 randconfig-a012
i386 randconfig-a014
i386 randconfig-a016
x86_64 randconfig-c001
arm randconfig-c002-20220925
i386 debian-10.3-kvm
i386 debian-10.3-kunit
i386 debian-10.3-func
riscv nommu_virt_defconfig
riscv rv32_defconfig
riscv nommu_k210_defconfig
i386 debian-10.3-kselftests
i386 debian-10.3
sh sh7763rdp_defconfig
csky defconfig
ia64 alldefconfig
powerpc asp8347_defconfig
s390 zfcpdump_defconfig
powerpc tqm8xx_defconfig
ia64 allmodconfig
i386 alldefconfig
mips bcm47xx_defconfig
sh urquell_defconfig
arc axs103_smp_defconfig
nios2 allyesconfig
nios2 defconfig
parisc defconfig
parisc64 defconfig
parisc allyesconfig
clang tested configs:
hexagon randconfig-r045-20220925
hexagon randconfig-r041-20220926
hexagon randconfig-r045-20220926
hexagon randconfig-r041-20220925
riscv randconfig-r042-20220926
i386 randconfig-a011-20220926
s390 randconfig-r044-20220926
i386 randconfig-a014-20220926
i386 randconfig-a013-20220926
i386 randconfig-a012-20220926
i386 randconfig-a015-20220926
i386 randconfig-a016-20220926
x86_64 randconfig-a012-20220926
x86_64 randconfig-a014-20220926
x86_64 randconfig-a013-20220926
x86_64 randconfig-a011-20220926
x86_64 randconfig-a001
x86_64 randconfig-a015-20220926
x86_64 randconfig-a016-20220926
x86_64 randconfig-a003
x86_64 randconfig-a005
x86_64 randconfig-k001
arm s5pv210_defconfig
arm vexpress_defconfig
mips qi_lb60_defconfig
powerpc ppc44x_defconfig
powerpc microwatt_defconfig
mips ath25_defconfig
arm davinci_all_defconfig
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-27 19:49 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=633353ba.dWfgoGvhn3zWooiU%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).