From: kernel test robot <lkp at intel.com>
To: devel@acpica.org
Subject: [Devel] [rafael-pm:bleeding-edge] BUILD SUCCESS f569faad1ef4d4f88432e6d5efba2562e0d1bc1f
Date: Thu, 01 Sep 2022 15:56:16 +0800 [thread overview]
Message-ID: <631065a0.1f0caBq0YvTQRxgc%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2960 bytes --]
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
branch HEAD: f569faad1ef4d4f88432e6d5efba2562e0d1bc1f Merge branch 'thermal-core' into bleeding-edge
elapsed time: 722m
configs tested: 53
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
arc randconfig-r043-20220831
s390 randconfig-r044-20220831
riscv randconfig-r042-20220831
x86_64 defconfig
powerpc allnoconfig
mips allyesconfig
powerpc allmodconfig
x86_64 randconfig-a013
x86_64 randconfig-a011
x86_64 rhel-8.3
x86_64 randconfig-a015
alpha allyesconfig
arc allyesconfig
sh allmodconfig
i386 randconfig-a001
i386 randconfig-a003
i386 randconfig-a005
x86_64 allyesconfig
i386 defconfig
x86_64 rhel-8.3-kselftests
x86_64 rhel-8.3-func
x86_64 rhel-8.3-kunit
m68k allyesconfig
i386 randconfig-a014
m68k allmodconfig
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-kvm
i386 randconfig-a012
i386 randconfig-a016
x86_64 randconfig-a004
x86_64 randconfig-a002
arm defconfig
x86_64 randconfig-a006
i386 allyesconfig
arm64 allyesconfig
arm allyesconfig
ia64 allmodconfig
clang tested configs:
hexagon randconfig-r041-20220831
hexagon randconfig-r045-20220831
x86_64 randconfig-a016
x86_64 randconfig-a012
x86_64 randconfig-a014
i386 randconfig-a002
i386 randconfig-a004
i386 randconfig-a006
i386 randconfig-a013
i386 randconfig-a011
i386 randconfig-a015
x86_64 randconfig-a001
x86_64 randconfig-a003
x86_64 randconfig-a005
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-01 7: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=631065a0.1f0caBq0YvTQRxgc%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).