From: kernel test robot <lkp at intel.com>
To: devel@acpica.org
Subject: [Devel] [pm:bleeding-edge] BUILD SUCCESS 83f7a626aa4d238dd3897065384eda829f14a005
Date: Wed, 05 Aug 2020 13:57:24 +0800 [thread overview]
Message-ID: <5f2a4a44.6chRtUahZM9dC9O2%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4433 bytes --]
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
branch HEAD: 83f7a626aa4d238dd3897065384eda829f14a005 Merge branch 'pm-cpufreq' into bleeding-edge
elapsed time: 803m
configs tested: 84
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
arm defconfig
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
arm allmodconfig
arm pxa3xx_defconfig
x86_64 allyesconfig
m68k amcore_defconfig
mips decstation_64_defconfig
arm viper_defconfig
parisc alldefconfig
arm h3600_defconfig
sh edosk7760_defconfig
mips vocore2_defconfig
sh kfr2r09_defconfig
m68k m5208evb_defconfig
mips jmr3927_defconfig
arm badge4_defconfig
arm pxa168_defconfig
arm alldefconfig
c6x evmc6457_defconfig
mips qi_lb60_defconfig
alpha defconfig
sh se7619_defconfig
sh rts7751r2dplus_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 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 defconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a005-20200805
i386 randconfig-a004-20200805
i386 randconfig-a001-20200805
i386 randconfig-a003-20200805
i386 randconfig-a002-20200805
i386 randconfig-a006-20200805
x86_64 randconfig-a013-20200805
x86_64 randconfig-a011-20200805
x86_64 randconfig-a012-20200805
x86_64 randconfig-a016-20200805
x86_64 randconfig-a015-20200805
x86_64 randconfig-a014-20200805
i386 randconfig-a011-20200805
i386 randconfig-a012-20200805
i386 randconfig-a013-20200805
i386 randconfig-a014-20200805
i386 randconfig-a015-20200805
i386 randconfig-a016-20200805
riscv allyesconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
x86_64 rhel
x86_64 rhel-7.6-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
WARNING: multiple messages have this Message-ID (diff)
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 83f7a626aa4d238dd3897065384eda829f14a005
Date: Wed, 05 Aug 2020 13:57:24 +0800 [thread overview]
Message-ID: <5f2a4a44.6chRtUahZM9dC9O2%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
branch HEAD: 83f7a626aa4d238dd3897065384eda829f14a005 Merge branch 'pm-cpufreq' into bleeding-edge
elapsed time: 803m
configs tested: 84
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
arm defconfig
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
arm allmodconfig
arm pxa3xx_defconfig
x86_64 allyesconfig
m68k amcore_defconfig
mips decstation_64_defconfig
arm viper_defconfig
parisc alldefconfig
arm h3600_defconfig
sh edosk7760_defconfig
mips vocore2_defconfig
sh kfr2r09_defconfig
m68k m5208evb_defconfig
mips jmr3927_defconfig
arm badge4_defconfig
arm pxa168_defconfig
arm alldefconfig
c6x evmc6457_defconfig
mips qi_lb60_defconfig
alpha defconfig
sh se7619_defconfig
sh rts7751r2dplus_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 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 defconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a005-20200805
i386 randconfig-a004-20200805
i386 randconfig-a001-20200805
i386 randconfig-a003-20200805
i386 randconfig-a002-20200805
i386 randconfig-a006-20200805
x86_64 randconfig-a013-20200805
x86_64 randconfig-a011-20200805
x86_64 randconfig-a012-20200805
x86_64 randconfig-a016-20200805
x86_64 randconfig-a015-20200805
x86_64 randconfig-a014-20200805
i386 randconfig-a011-20200805
i386 randconfig-a012-20200805
i386 randconfig-a013-20200805
i386 randconfig-a014-20200805
i386 randconfig-a015-20200805
i386 randconfig-a016-20200805
riscv allyesconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
x86_64 rhel
x86_64 rhel-7.6-kselftests
x86_64 defconfig
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
next reply other threads:[~2020-08-05 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 5:57 kernel test robot [this message]
2020-08-05 5:57 ` [pm:bleeding-edge] BUILD SUCCESS 83f7a626aa4d238dd3897065384eda829f14a005 kernel test robot
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=5f2a4a44.6chRtUahZM9dC9O2%lkp@intel.com \
--to=devel@acpica.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.