From: kernel test robot <lkp at intel.com>
To: devel@acpica.org
Subject: [Devel] [rafael-pm:bleeding-edge] BUILD SUCCESS 392b72b87ef168779f8651662155dc60e723d491
Date: Mon, 26 Sep 2022 11:56:08 +0800 [thread overview]
Message-ID: <633122d8.gE3EroSeVgRKEsTv%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3207 bytes --]
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
branch HEAD: 392b72b87ef168779f8651662155dc60e723d491 Merge branches 'pm-core' and 'powercap' into bleeding-edge
elapsed time: 725m
configs tested: 58
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
um i386_defconfig
um x86_64_defconfig
x86_64 rhel-8.3-func
x86_64 rhel-8.3-kselftests
x86_64 defconfig
i386 defconfig
arc randconfig-r043-20220925
i386 randconfig-a001
i386 randconfig-a003
arc defconfig
powerpc allmodconfig
arm defconfig
i386 randconfig-a005
sh allmodconfig
x86_64 rhel-8.3-syz
s390 randconfig-r044-20220925
x86_64 rhel-8.3-kunit
alpha defconfig
riscv randconfig-r042-20220925
mips allyesconfig
x86_64 rhel-8.3-kvm
x86_64 randconfig-a002
x86_64 randconfig-a015
powerpc allnoconfig
x86_64 randconfig-a013
x86_64 rhel-8.3
arm allyesconfig
s390 allmodconfig
x86_64 randconfig-a011
i386 randconfig-a012
i386 randconfig-a014
x86_64 randconfig-a004
arm64 allyesconfig
i386 randconfig-a016
x86_64 randconfig-a006
x86_64 allyesconfig
s390 defconfig
m68k allyesconfig
ia64 allmodconfig
i386 allyesconfig
m68k allmodconfig
arc allyesconfig
s390 allyesconfig
alpha allyesconfig
clang tested configs:
hexagon randconfig-r045-20220925
i386 randconfig-a002
hexagon randconfig-r041-20220925
i386 randconfig-a006
x86_64 randconfig-a001
x86_64 randconfig-a014
i386 randconfig-a013
i386 randconfig-a004
i386 randconfig-a011
x86_64 randconfig-a003
x86_64 randconfig-a012
x86_64 randconfig-a016
x86_64 randconfig-a005
i386 randconfig-a015
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-26 3:56 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=633122d8.gE3EroSeVgRKEsTv%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 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 read-only IMAP folder(s) and NNTP newsgroup(s).