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 5d422cd4fc8e5853cb3dc8d7c648a9eb8a04bee9
Date: Sun, 18 Oct 2020 13:34:15 +0800 [thread overview]
Message-ID: <5f8bd3d7.L4V4GYOBUjDsQv7A%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-testing
branch HEAD: 5d422cd4fc8e5853cb3dc8d7c648a9eb8a04bee9 staging: qlge: remove extra blank lines
elapsed time: 721m
configs tested: 94
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
arm imx_v4_v5_defconfig
mips workpad_defconfig
xtensa smp_lx200_defconfig
xtensa audio_kc705_defconfig
mips decstation_r4k_defconfig
arm collie_defconfig
m68k mvme16x_defconfig
sparc64 defconfig
mips capcella_defconfig
arm assabet_defconfig
mips decstation_64_defconfig
arm pxa168_defconfig
arm clps711x_defconfig
sh kfr2r09-romimage_defconfig
arm tct_hammer_defconfig
arm milbeaut_m10v_defconfig
arm lubbock_defconfig
m68k mac_defconfig
arm sunxi_defconfig
arc axs103_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a006-20201018
i386 randconfig-a005-20201018
i386 randconfig-a001-20201018
i386 randconfig-a003-20201018
i386 randconfig-a004-20201018
i386 randconfig-a002-20201018
x86_64 randconfig-a016-20201018
x86_64 randconfig-a015-20201018
x86_64 randconfig-a012-20201018
x86_64 randconfig-a013-20201018
x86_64 randconfig-a011-20201018
x86_64 randconfig-a014-20201018
i386 randconfig-a015-20201018
i386 randconfig-a013-20201018
i386 randconfig-a016-20201018
i386 randconfig-a012-20201018
i386 randconfig-a011-20201018
i386 randconfig-a014-20201018
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
x86_64 rhel
x86_64 allyesconfig
x86_64 rhel-7.6-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
clang tested configs:
x86_64 randconfig-a004-20201018
x86_64 randconfig-a002-20201018
x86_64 randconfig-a006-20201018
x86_64 randconfig-a003-20201018
x86_64 randconfig-a005-20201018
x86_64 randconfig-a001-20201018
---
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:[~2020-10-18 5:35 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=5f8bd3d7.L4V4GYOBUjDsQv7A%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 NNTP newsgroup(s).