From: kernel test robot <lkp@intel.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: linux-serial@vger.kernel.org
Subject: [tty:tty-testing] BUILD SUCCESS 8f49a2fe8e6bccbd47555048def9cd08da220c74
Date: Tue, 01 Sep 2020 02:24:51 +0800 [thread overview]
Message-ID: <5f4d4073.CabEUXnaXg0pH0aI%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
branch HEAD: 8f49a2fe8e6bccbd47555048def9cd08da220c74 Merge 5.9-rc3 into tty-next
elapsed time: 782m
configs tested: 111
configs skipped: 8
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
xtensa allyesconfig
arm mmp2_defconfig
m68k mvme147_defconfig
um kunit_defconfig
mips decstation_r4k_defconfig
arc axs103_smp_defconfig
riscv allyesconfig
mips rb532_defconfig
arm viper_defconfig
arm colibri_pxa300_defconfig
mips workpad_defconfig
mips cu1830-neo_defconfig
arm shmobile_defconfig
powerpc wii_defconfig
mips sb1250_swarm_defconfig
sh se7206_defconfig
sh defconfig
c6x evmc6472_defconfig
mips nlm_xlp_defconfig
m68k m5208evb_defconfig
mips rm200_defconfig
mips cu1000-neo_defconfig
riscv defconfig
arm pxa_defconfig
mips maltasmvp_eva_defconfig
mips omega2p_defconfig
arc nps_defconfig
ia64 bigsur_defconfig
powerpc ps3_defconfig
arm s3c6400_defconfig
sh sh7785lcr_defconfig
arm orion5x_defconfig
powerpc mpc5200_defconfig
sh sh7770_generic_defconfig
powerpc mpc83xx_defconfig
m68k sun3_defconfig
mips jmr3927_defconfig
arm ixp4xx_defconfig
ia64 alldefconfig
m68k stmark2_defconfig
arm nhk8815_defconfig
sh rts7751r2d1_defconfig
arm qcom_defconfig
mips decstation_defconfig
arm clps711x_defconfig
nds32 allnoconfig
parisc generic-64bit_defconfig
xtensa defconfig
arm alldefconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
c6x allyesconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc 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 allnoconfig
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-08-31 18:25 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=5f4d4073.CabEUXnaXg0pH0aI%lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@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).