From: kbuild test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:pending-fixes] BUILD SUCCESS 3a0f8793ae13e69da6ef8c43421832d2f1f1acd0
Date: Sat, 11 Apr 2020 01:38:05 +0800 [thread overview]
Message-ID: <5e90aefd.mJlR1IFKiVzJAXpu%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: 3a0f8793ae13e69da6ef8c43421832d2f1f1acd0 Merge remote-tracking branch 'drm-misc-fixes/for-linux-next-fixes'
elapsed time: 905m
configs tested: 107
configs skipped: 0
The following configs have been built successfully.
More configs may be tested in the coming days.
arm64 allyesconfig
arm allyesconfig
arm64 allmodconfig
arm allmodconfig
arm64 allnoconfig
arm allnoconfig
arm efm32_defconfig
arm at91_dt_defconfig
arm shmobile_defconfig
arm64 defconfig
arm exynos_defconfig
arm multi_v5_defconfig
arm sunxi_defconfig
arm multi_v7_defconfig
riscv defconfig
s390 defconfig
arc defconfig
c6x evmc6678_defconfig
m68k m5475evb_defconfig
sh rsk7269_defconfig
i386 allyesconfig
parisc generic-32bit_defconfig
i386 allnoconfig
i386 alldefconfig
i386 defconfig
i386 debian-10.3
ia64 allmodconfig
ia64 defconfig
ia64 allnoconfig
ia64 allyesconfig
ia64 alldefconfig
xtensa iss_defconfig
xtensa common_defconfig
nds32 defconfig
nds32 allnoconfig
csky defconfig
alpha defconfig
h8300 h8s-sim_defconfig
h8300 edosk2674_defconfig
m68k allmodconfig
h8300 h8300h-sim_defconfig
m68k sun3_defconfig
m68k multi_defconfig
arc allyesconfig
mips fuloong2e_defconfig
mips malta_kvm_defconfig
parisc allnoconfig
parisc generic-64bit_defconfig
parisc allyesconfig
i386 randconfig-a002-20200410
x86_64 randconfig-a001-20200410
x86_64 randconfig-a002-20200410
mips randconfig-a001-20200410
nds32 randconfig-a001-20200410
m68k randconfig-a001-20200410
riscv randconfig-a001-20200410
alpha randconfig-a001-20200410
parisc randconfig-a001-20200410
h8300 randconfig-a001-20200410
nios2 randconfig-a001-20200410
c6x randconfig-a001-20200410
csky randconfig-a001-20200410
openrisc randconfig-a001-20200410
s390 randconfig-a001-20200410
sh randconfig-a001-20200410
xtensa randconfig-a001-20200410
x86_64 randconfig-b002-20200410
x86_64 randconfig-c003-20200410
i386 randconfig-c003-20200410
i386 randconfig-c002-20200410
i386 randconfig-c001-20200410
x86_64 randconfig-h001-20200410
powerpc randconfig-a001-20200410
arm64 randconfig-a001-20200410
ia64 randconfig-a001-20200410
arc randconfig-a001-20200410
sparc randconfig-a001-20200410
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv rv32_defconfig
riscv allmodconfig
s390 zfcpdump_defconfig
s390 debug_defconfig
s390 allyesconfig
s390 allnoconfig
s390 allmodconfig
s390 alldefconfig
sh allmodconfig
sh allnoconfig
sh sh7785lcr_32bit_defconfig
sh titan_defconfig
sparc allyesconfig
sparc defconfig
sparc64 defconfig
sparc64 allnoconfig
sparc64 allyesconfig
sparc64 allmodconfig
um x86_64_defconfig
um i386_defconfig
um defconfig
x86_64 rhel
x86_64 rhel-7.6
x86_64 rhel-7.2-clear
x86_64 lkp
x86_64 fedora-25
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-04-10 17:39 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=5e90aefd.mJlR1IFKiVzJAXpu%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--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