From: kernel test robot <lkp@intel.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org
Subject: [staging:staging-testing] BUILD SUCCESS 76e78f3df8f5d21b1a85f770fa92a1fd211e429b
Date: Sat, 15 May 2021 08:25:38 +0800 [thread overview]
Message-ID: <609f1502.8Y/1JynfnGhF1BmW%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-testing
branch HEAD: 76e78f3df8f5d21b1a85f770fa92a1fd211e429b staging: unisys: visorinput: remove redundant assignment of variable led
elapsed time: 723m
configs tested: 105
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm defconfig
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
arm allmodconfig
powerpc socrates_defconfig
parisc generic-64bit_defconfig
mips rb532_defconfig
mips nlm_xlr_defconfig
sh sh7785lcr_32bit_defconfig
sh se7721_defconfig
arm mainstone_defconfig
powerpc mgcoge_defconfig
arm exynos_defconfig
powerpc ppa8548_defconfig
sh magicpanelr2_defconfig
arm davinci_all_defconfig
mips tb0219_defconfig
m68k m5275evb_defconfig
sh sh2007_defconfig
m68k m5272c3_defconfig
powerpc mpc836x_mds_defconfig
arc defconfig
m68k m5249evb_defconfig
m68k sun3_defconfig
powerpc mpc512x_defconfig
openrisc simple_smp_defconfig
mips ip22_defconfig
arc axs101_defconfig
m68k hp300_defconfig
powerpc wii_defconfig
riscv rv32_defconfig
xtensa nommu_kc705_defconfig
x86_64 allnoconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
s390 allmodconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a004-20210514
x86_64 randconfig-a003-20210514
x86_64 randconfig-a001-20210514
x86_64 randconfig-a005-20210514
x86_64 randconfig-a002-20210514
x86_64 randconfig-a006-20210514
i386 randconfig-a003-20210514
i386 randconfig-a001-20210514
i386 randconfig-a004-20210514
i386 randconfig-a005-20210514
i386 randconfig-a002-20210514
i386 randconfig-a006-20210514
i386 randconfig-a016-20210514
i386 randconfig-a014-20210514
i386 randconfig-a011-20210514
i386 randconfig-a012-20210514
i386 randconfig-a015-20210514
i386 randconfig-a013-20210514
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
um allmodconfig
um allnoconfig
um allyesconfig
um defconfig
x86_64 allyesconfig
x86_64 rhel-8.3-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-kbuiltin
x86_64 kexec
clang tested configs:
x86_64 randconfig-a015-20210514
x86_64 randconfig-a012-20210514
x86_64 randconfig-a011-20210514
x86_64 randconfig-a013-20210514
x86_64 randconfig-a016-20210514
x86_64 randconfig-a014-20210514
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
reply other threads:[~2021-05-15 0:26 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=609f1502.8Y/1JynfnGhF1BmW%lkp@intel.com \
--to=lkp@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).