From: kernel test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Brown <broonie@sirena.org.uk>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:pending-fixes] BUILD SUCCESS 80ff4c1575913e69caf833eebe6c58a46891c594
Date: Tue, 27 Jul 2021 20:26:45 +0800 [thread overview]
Message-ID: <60fffb85.wOsrwOcDVL9B3/l9%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: 80ff4c1575913e69caf833eebe6c58a46891c594 Merge remote-tracking branch 'drm-misc-fixes/for-linux-next-fixes'
elapsed time: 847m
configs tested: 100
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm defconfig
arm64 defconfig
arm64 allyesconfig
arm allyesconfig
arm allmodconfig
powerpc mpc8313_rdb_defconfig
powerpc g5_defconfig
mips rs90_defconfig
m68k mvme147_defconfig
sh magicpanelr2_defconfig
riscv nommu_virt_defconfig
powerpc linkstation_defconfig
sparc defconfig
sh r7785rp_defconfig
ia64 tiger_defconfig
arm spitz_defconfig
ia64 alldefconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
x86_64 allnoconfig
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
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a005-20210726
i386 randconfig-a003-20210726
i386 randconfig-a004-20210726
i386 randconfig-a002-20210726
i386 randconfig-a001-20210726
i386 randconfig-a006-20210726
i386 randconfig-a005-20210727
i386 randconfig-a003-20210727
i386 randconfig-a004-20210727
i386 randconfig-a002-20210727
i386 randconfig-a001-20210727
i386 randconfig-a006-20210727
x86_64 randconfig-a011-20210727
x86_64 randconfig-a016-20210727
x86_64 randconfig-a013-20210727
x86_64 randconfig-a014-20210727
x86_64 randconfig-a012-20210727
x86_64 randconfig-a015-20210727
i386 randconfig-a016-20210727
i386 randconfig-a013-20210727
i386 randconfig-a012-20210727
i386 randconfig-a011-20210727
i386 randconfig-a014-20210727
i386 randconfig-a015-20210727
i386 randconfig-a016-20210726
i386 randconfig-a013-20210726
i386 randconfig-a012-20210726
i386 randconfig-a011-20210726
i386 randconfig-a014-20210726
i386 randconfig-a015-20210726
riscv nommu_k210_defconfig
riscv allyesconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
um x86_64_defconfig
um i386_defconfig
x86_64 allyesconfig
x86_64 rhel-8.3-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
clang tested configs:
x86_64 randconfig-c001-20210726
x86_64 randconfig-a011-20210726
x86_64 randconfig-a016-20210726
x86_64 randconfig-a013-20210726
x86_64 randconfig-a014-20210726
x86_64 randconfig-a012-20210726
x86_64 randconfig-a015-20210726
x86_64 randconfig-a003-20210727
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-07-27 12:27 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=60fffb85.wOsrwOcDVL9B3/l9%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@sirena.org.uk \
--cc=linux-mm@kvack.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