From: kernel test robot <lkp@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org, devel@acpica.org, linux-acpi@vger.kernel.org
Subject: [pm:bleeding-edge] BUILD SUCCESS 5e46e56c2b0018fe280a88cdb424165c3fe59ba0
Date: Tue, 06 Oct 2020 14:41:55 +0800 [thread overview]
Message-ID: <5f7c11b3.wuZFSnBcDzgYepc+%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
branch HEAD: 5e46e56c2b0018fe280a88cdb424165c3fe59ba0 Merge branch 'pm-sleep' into bleeding-edge
elapsed time: 721m
configs tested: 93
configs skipped: 2
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
arm cm_x300_defconfig
powerpc pasemi_defconfig
mips bmips_stb_defconfig
powerpc cm5200_defconfig
powerpc stx_gp3_defconfig
sh se7721_defconfig
mips fuloong2e_defconfig
mips pic32mzda_defconfig
sh microdev_defconfig
arm versatile_defconfig
powerpc skiroot_defconfig
powerpc chrp32_defconfig
mips malta_qemu_32r6_defconfig
arm palmz72_defconfig
arm ixp4xx_defconfig
mips jmr3927_defconfig
arm vf610m4_defconfig
mips ath25_defconfig
powerpc canyonlands_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa 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
i386 randconfig-a006-20201005
i386 randconfig-a005-20201005
i386 randconfig-a001-20201005
i386 randconfig-a004-20201005
i386 randconfig-a003-20201005
i386 randconfig-a002-20201005
x86_64 randconfig-a012-20201005
x86_64 randconfig-a015-20201005
x86_64 randconfig-a014-20201005
x86_64 randconfig-a013-20201005
x86_64 randconfig-a011-20201005
x86_64 randconfig-a016-20201005
i386 randconfig-a014-20201005
i386 randconfig-a015-20201005
i386 randconfig-a013-20201005
i386 randconfig-a016-20201005
i386 randconfig-a011-20201005
i386 randconfig-a012-20201005
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
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
clang tested configs:
x86_64 randconfig-a004-20201005
x86_64 randconfig-a002-20201005
x86_64 randconfig-a001-20201005
x86_64 randconfig-a003-20201005
x86_64 randconfig-a005-20201005
x86_64 randconfig-a006-20201005
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-10-06 6:42 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=5f7c11b3.wuZFSnBcDzgYepc+%lkp@intel.com \
--to=lkp@intel.com \
--cc=devel@acpica.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).