From: kernel test robot <lkp@intel.com>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [gustavoars-linux:testing/fam0] BUILD SUCCESS a56dbff00095f3fc2c3fcb71dab2e536d42a4ff5
Date: Tue, 01 Sep 2020 12:10:40 +0800 [thread overview]
Message-ID: <5f4dc9c0.xY5yZXesL5ePuzmL%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git testing/fam0
branch HEAD: a56dbff00095f3fc2c3fcb71dab2e536d42a4ff5 scsi: target: tcmu: Replace zero-length array with flexible-array member
elapsed time: 726m
configs tested: 116
configs skipped: 7
The following configs have been built successfully.
More configs may be tested in the coming days.
arm defconfig
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
arm allmodconfig
arm hackkit_defconfig
powerpc pq2fads_defconfig
arm h3600_defconfig
sh se7712_defconfig
powerpc64 alldefconfig
openrisc alldefconfig
m68k mac_defconfig
powerpc pmac32_defconfig
sh lboxre2_defconfig
sh se7751_defconfig
arm u8500_defconfig
parisc generic-32bit_defconfig
m68k mvme147_defconfig
powerpc allmodconfig
m68k apollo_defconfig
sh r7785rp_defconfig
powerpc mpc83xx_defconfig
powerpc allyesconfig
csky defconfig
arm mini2440_defconfig
arm cerfcube_defconfig
h8300 defconfig
arm spear13xx_defconfig
arc defconfig
m68k sun3x_defconfig
arm u300_defconfig
parisc allyesconfig
mips capcella_defconfig
powerpc ppc6xx_defconfig
sh rts7751r2d1_defconfig
m68k q40_defconfig
arm omap1_defconfig
arm milbeaut_m10v_defconfig
sh edosk7705_defconfig
mips malta_kvm_defconfig
sh microdev_defconfig
mips bmips_stb_defconfig
arm mps2_defconfig
nios2 defconfig
arm imx_v6_v7_defconfig
mips rs90_defconfig
i386 alldefconfig
powerpc ppc64e_defconfig
arm hisi_defconfig
nios2 3c120_defconfig
powerpc adder875_defconfig
sh titan_defconfig
mips gcw0_defconfig
arm bcm2835_defconfig
arc hsdk_defconfig
arm s5pv210_defconfig
powerpc wii_defconfig
sh sh7757lcr_defconfig
sh alldefconfig
arm stm32_defconfig
mips jmr3927_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
nds32 defconfig
nios2 allyesconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allnoconfig
powerpc defconfig
i386 randconfig-a001-20200831
i386 randconfig-a002-20200831
i386 randconfig-a004-20200831
i386 randconfig-a006-20200831
i386 randconfig-a005-20200831
i386 randconfig-a003-20200831
x86_64 randconfig-a012-20200831
x86_64 randconfig-a015-20200831
x86_64 randconfig-a014-20200831
x86_64 randconfig-a011-20200831
x86_64 randconfig-a016-20200831
x86_64 randconfig-a013-20200831
i386 randconfig-a013-20200831
i386 randconfig-a011-20200831
i386 randconfig-a012-20200831
i386 randconfig-a015-20200831
i386 randconfig-a016-20200831
i386 randconfig-a014-20200831
riscv allyesconfig
riscv allnoconfig
riscv 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
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-09-01 4:11 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=5f4dc9c0.xY5yZXesL5ePuzmL%lkp@intel.com \
--to=lkp@intel.com \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@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
Powered by JetHome