From: kernel test robot <lkp@intel.com>
To: Gao Xiang <xiang@kernel.org>
Cc: linux-erofs@lists.ozlabs.org
Subject: [xiang-erofs:erofs/dax] BUILD SUCCESS 9b6f5b986ca553d44303783ce495a60ae0c390a6
Date: Sat, 31 Jul 2021 13:53:25 +0800 [thread overview]
Message-ID: <6104e555.VkEwoHxeWjTa8ZE/%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git erofs/dax
branch HEAD: 9b6f5b986ca553d44303783ce495a60ae0c390a6 erofs: convert all uncompressed cases to iomap
elapsed time: 723m
configs tested: 108
configs skipped: 4
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
i386 randconfig-c001-20210730
mips pic32mzda_defconfig
mips malta_defconfig
h8300 alldefconfig
arm collie_defconfig
powerpc ppa8548_defconfig
arm sunxi_defconfig
arm eseries_pxa_defconfig
m68k sun3_defconfig
parisc allyesconfig
arm simpad_defconfig
mips sb1250_swarm_defconfig
h8300 edosk2674_defconfig
arm mainstone_defconfig
arm dove_defconfig
sh edosk7705_defconfig
mips ip28_defconfig
m68k q40_defconfig
nios2 10m50_defconfig
arm pcm027_defconfig
powerpc wii_defconfig
arc alldefconfig
sh se7705_defconfig
mips mtx1_defconfig
x86_64 alldefconfig
powerpc gamecube_defconfig
powerpc currituck_defconfig
powerpc chrp32_defconfig
mips fuloong2e_defconfig
sh ecovec24-romimage_defconfig
mips rs90_defconfig
arm footbridge_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
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
s390 allmodconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a005-20210730
i386 randconfig-a004-20210730
i386 randconfig-a003-20210730
i386 randconfig-a002-20210730
i386 randconfig-a006-20210730
i386 randconfig-a001-20210730
x86_64 randconfig-a015-20210730
x86_64 randconfig-a014-20210730
x86_64 randconfig-a013-20210730
x86_64 randconfig-a011-20210730
x86_64 randconfig-a012-20210730
x86_64 randconfig-a016-20210730
i386 randconfig-a013-20210730
i386 randconfig-a016-20210730
i386 randconfig-a012-20210730
i386 randconfig-a011-20210730
i386 randconfig-a014-20210730
i386 randconfig-a015-20210730
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
x86_64 rhel-8.3-kselftests
um x86_64_defconfig
um i386_defconfig
x86_64 allyesconfig
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
clang tested configs:
x86_64 randconfig-c001-20210730
x86_64 randconfig-a001-20210730
x86_64 randconfig-a006-20210730
x86_64 randconfig-a005-20210730
x86_64 randconfig-a004-20210730
x86_64 randconfig-a002-20210730
x86_64 randconfig-a003-20210730
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-07-31 5:55 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=6104e555.VkEwoHxeWjTa8ZE/%lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=xiang@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).