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: [rafael-pm:bleeding-edge] BUILD SUCCESS aaa3a53c4b473a78e8cc8682c22030674d48fe5f
Date: Thu, 16 Dec 2021 13:58:55 +0800 [thread overview]
Message-ID: <61bad59f.DvT915NBPrMwrPVN%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
branch HEAD: aaa3a53c4b473a78e8cc8682c22030674d48fe5f Merge branch 'acpi-tables' into bleeding-edge
elapsed time: 728m
configs tested: 103
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm allyesconfig
arm allmodconfig
arm defconfig
arm64 defconfig
arm64 allyesconfig
powerpc pasemi_defconfig
arm exynos_defconfig
arm lpd270_defconfig
powerpc cm5200_defconfig
m68k m5275evb_defconfig
arm dove_defconfig
powerpc cell_defconfig
m68k stmark2_defconfig
sh lboxre2_defconfig
m68k m5407c3_defconfig
mips jazz_defconfig
powerpc asp8347_defconfig
m68k mvme147_defconfig
xtensa nommu_kc705_defconfig
arm shannon_defconfig
sh landisk_defconfig
powerpc adder875_defconfig
mips pic32mzda_defconfig
arm mmp2_defconfig
arm randconfig-c002-20211214
ia64 defconfig
ia64 allmodconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nds32 defconfig
csky defconfig
alpha defconfig
alpha allyesconfig
nios2 allyesconfig
arc defconfig
sh allmodconfig
h8300 allyesconfig
xtensa allyesconfig
parisc defconfig
s390 allmodconfig
parisc allyesconfig
s390 defconfig
s390 allyesconfig
i386 allyesconfig
sparc defconfig
i386 defconfig
i386 debian-10.3-kselftests
i386 debian-10.3
sparc allyesconfig
nds32 allnoconfig
nios2 defconfig
arc allyesconfig
mips allyesconfig
mips allmodconfig
powerpc allnoconfig
powerpc allmodconfig
powerpc allyesconfig
x86_64 randconfig-a001-20211214
x86_64 randconfig-a002-20211214
x86_64 randconfig-a003-20211214
x86_64 randconfig-a004-20211214
x86_64 randconfig-a006-20211214
x86_64 randconfig-a005-20211214
i386 randconfig-a001-20211214
i386 randconfig-a002-20211214
i386 randconfig-a005-20211214
i386 randconfig-a003-20211214
i386 randconfig-a006-20211214
i386 randconfig-a004-20211214
arc randconfig-r043-20211214
riscv nommu_k210_defconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
riscv allyesconfig
um i386_defconfig
um x86_64_defconfig
x86_64 allyesconfig
x86_64 defconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-func
x86_64 kexec
x86_64 rhel-8.3-kselftests
clang tested configs:
x86_64 randconfig-a011-20211214
x86_64 randconfig-a014-20211214
x86_64 randconfig-a012-20211214
x86_64 randconfig-a013-20211214
x86_64 randconfig-a016-20211214
x86_64 randconfig-a015-20211214
i386 randconfig-a013-20211214
i386 randconfig-a011-20211214
i386 randconfig-a016-20211214
i386 randconfig-a014-20211214
i386 randconfig-a015-20211214
i386 randconfig-a012-20211214
hexagon randconfig-r045-20211214
s390 randconfig-r044-20211214
riscv randconfig-r042-20211214
hexagon randconfig-r041-20211214
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-16 5: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=61bad59f.DvT915NBPrMwrPVN%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