From: kbuild test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Brown <broonie@kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:pending-fixes] BUILD SUCCESS ec3b4fcb56c6cbd4d7e6efd5cd99708fd3569d7b
Date: Thu, 26 Sep 2019 04:59:10 +0800 [thread overview]
Message-ID: <5d8bd51e.Lj+XvkzPTBdqIgIu%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: ec3b4fcb56c6cbd4d7e6efd5cd99708fd3569d7b Merge remote-tracking branch 'drm-misc-fixes/for-linux-next-fixes'
elapsed time: 81m
configs tested: 105
The following configs have been built successfully.
More configs may be tested in the coming days.
arm allmodconfig
arm allnoconfig
arm at91_dt_defconfig
arm efm32_defconfig
arm exynos_defconfig
arm multi_v5_defconfig
arm multi_v7_defconfig
arm shmobile_defconfig
arm sunxi_defconfig
arm64 allmodconfig
arm64 allnoconfig
arm64 allyesconfig
arm64 defconfig
x86_64 fedora-25
x86_64 kexec
x86_64 lkp
x86_64 rhel
x86_64 rhel-7.6
i386 alldefconfig
i386 allnoconfig
i386 defconfig
um defconfig
um i386_defconfig
um x86_64_defconfig
x86_64 randconfig-b001-201938
x86_64 randconfig-b002-201938
x86_64 randconfig-b003-201938
x86_64 randconfig-b004-201938
i386 randconfig-b001-201938
i386 randconfig-b002-201938
i386 randconfig-b003-201938
i386 randconfig-b004-201938
h8300 edosk2674_defconfig
h8300 h8300h-sim_defconfig
h8300 h8s-sim_defconfig
m68k allmodconfig
m68k m5475evb_defconfig
m68k multi_defconfig
m68k sun3_defconfig
sparc defconfig
sparc64 allmodconfig
sparc64 allnoconfig
sparc64 defconfig
x86_64 allyesconfig
i386 allmodconfig
ia64 alldefconfig
ia64 allmodconfig
ia64 allnoconfig
ia64 defconfig
s390 allmodconfig
s390 allnoconfig
s390 debug_defconfig
s390 defconfig
x86_64 randconfig-f001-201938
x86_64 randconfig-f002-201938
x86_64 randconfig-f003-201938
x86_64 randconfig-f004-201938
i386 randconfig-f001-201938
i386 randconfig-f002-201938
i386 randconfig-f003-201938
i386 randconfig-f004-201938
mips 32r2_defconfig
mips 64r6el_defconfig
mips allmodconfig
mips allnoconfig
mips fuloong2e_defconfig
mips malta_kvm_defconfig
arc allyesconfig
arc defconfig
microblaze mmu_defconfig
microblaze nommu_defconfig
powerpc allnoconfig
powerpc defconfig
powerpc ppc64_defconfig
alpha defconfig
nds32 allnoconfig
nds32 defconfig
riscv allnoconfig
riscv defconfig
x86_64 randconfig-h003-201938
x86_64 randconfig-h002-201938
i386 randconfig-h001-201938
i386 randconfig-h002-201938
x86_64 randconfig-h004-201938
i386 randconfig-h004-201938
i386 randconfig-h003-201938
x86_64 randconfig-h001-201938
parisc allnoconfig
parisc b180_defconfig
parisc c3000_defconfig
parisc defconfig
c6x allyesconfig
c6x evmc6678_defconfig
nios2 10m50_defconfig
nios2 3c120_defconfig
openrisc or1ksim_defconfig
openrisc simple_smp_defconfig
xtensa common_defconfig
xtensa iss_defconfig
x86_64 allmodconfig
sh allmodconfig
sh allnoconfig
sh rsk7269_defconfig
sh sh7785lcr_32bit_defconfig
sh titan_defconfig
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
reply other threads:[~2019-09-25 20:59 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=5d8bd51e.Lj+XvkzPTBdqIgIu%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.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