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 13e16aa03377c16d68021fe5a6bae28c0f100551
Date: Tue, 14 Jul 2020 18:31:25 +0800 [thread overview]
Message-ID: <5f0d897d.9Fja5vLgrTaFOs/6%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
branch HEAD: 13e16aa03377c16d68021fe5a6bae28c0f100551 Merge branch 'pm-cpufreq-fixes' into bleeding-edge
elapsed time: 1079m
configs tested: 103
configs skipped: 5
The following configs have been built successfully.
More configs may be tested in the coming days.
arm64 allyesconfig
arm64 defconfig
arm64 allmodconfig
arm64 allnoconfig
arm defconfig
arm allyesconfig
arm allmodconfig
arm allnoconfig
m68k m5249evb_defconfig
m68k amcore_defconfig
h8300 defconfig
arm vt8500_v6_v7_defconfig
powerpc mpc5200_defconfig
arm sama5_defconfig
mips allnoconfig
sh apsh4ad0a_defconfig
arm am200epdkit_defconfig
xtensa common_defconfig
i386 allnoconfig
parisc allmodconfig
i386 allyesconfig
i386 defconfig
i386 debian-10.3
ia64 allmodconfig
ia64 defconfig
ia64 allnoconfig
ia64 allyesconfig
m68k allmodconfig
m68k allnoconfig
m68k sun3_defconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
nios2 allyesconfig
openrisc defconfig
c6x allyesconfig
c6x allnoconfig
openrisc allyesconfig
nds32 defconfig
nds32 allnoconfig
csky allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
h8300 allmodconfig
xtensa defconfig
arc defconfig
arc allyesconfig
sh allmodconfig
sh allnoconfig
microblaze allnoconfig
mips allyesconfig
mips allmodconfig
parisc allnoconfig
parisc defconfig
parisc allyesconfig
powerpc defconfig
powerpc allyesconfig
powerpc rhel-kconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a001-20200713
i386 randconfig-a005-20200713
i386 randconfig-a006-20200713
i386 randconfig-a002-20200713
i386 randconfig-a003-20200713
i386 randconfig-a004-20200713
i386 randconfig-a016-20200713
i386 randconfig-a015-20200713
i386 randconfig-a011-20200713
i386 randconfig-a012-20200713
i386 randconfig-a013-20200713
i386 randconfig-a014-20200713
x86_64 randconfig-a005-20200713
x86_64 randconfig-a002-20200713
x86_64 randconfig-a006-20200713
x86_64 randconfig-a001-20200713
x86_64 randconfig-a003-20200713
x86_64 randconfig-a004-20200713
riscv allyesconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
s390 allyesconfig
s390 allnoconfig
s390 allmodconfig
s390 defconfig
sparc allyesconfig
sparc defconfig
sparc64 defconfig
sparc64 allnoconfig
sparc64 allyesconfig
sparc64 allmodconfig
x86_64 rhel
x86_64 rhel-7.2-clear
x86_64 lkp
x86_64 fedora-25
x86_64 rhel-7.6
x86_64 rhel-7.6-kselftests
x86_64 rhel-8.3
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-07-14 10:32 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=5f0d897d.9Fja5vLgrTaFOs/6%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).