acpica-devel.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp at intel.com>
To: devel@acpica.org
Subject: [Devel] [rafael-pm:bleeding-edge] BUILD SUCCESS 816cee8cb69ed35afedc0a1011493e5f8c6aeead
Date: Sat, 01 Oct 2022 18:44:45 +0800	[thread overview]
Message-ID: <63381a1d.1RMK5Xirt7dxFPZ9%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3430 bytes --]

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
branch HEAD: 816cee8cb69ed35afedc0a1011493e5f8c6aeead  Merge branch 'thermal-core' into bleeding-edge

elapsed time: 979m

configs tested: 63
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-kvm
powerpc                           allnoconfig
x86_64                           rhel-8.3-syz
powerpc                          allmodconfig
x86_64                         rhel-8.3-kunit
arc                                 defconfig
mips                             allyesconfig
x86_64                          rhel-8.3-func
i386                                defconfig
x86_64                    rhel-8.3-kselftests
alpha                               defconfig
s390                             allmodconfig
arm                                 defconfig
m68k                             allmodconfig
s390                                defconfig
sh                               allmodconfig
arc                              allyesconfig
alpha                            allyesconfig
s390                             allyesconfig
m68k                             allyesconfig
x86_64                              defconfig
arc                  randconfig-r043-20220925
arm64                            allyesconfig
riscv                randconfig-r042-20220925
arm                              allyesconfig
i386                 randconfig-a001-20220926
arc                  randconfig-r043-20220926
x86_64               randconfig-a002-20220926
s390                 randconfig-r044-20220925
i386                 randconfig-a002-20220926
x86_64               randconfig-a005-20220926
x86_64                               rhel-8.3
i386                 randconfig-a003-20220926
x86_64               randconfig-a004-20220926
x86_64                        randconfig-a013
x86_64               randconfig-a006-20220926
x86_64                        randconfig-a011
i386                 randconfig-a004-20220926
i386                             allyesconfig
x86_64               randconfig-a001-20220926
i386                 randconfig-a005-20220926
i386                 randconfig-a006-20220926
x86_64               randconfig-a003-20220926
x86_64                        randconfig-a015
x86_64                           allyesconfig
ia64                             allmodconfig

clang tested configs:
hexagon              randconfig-r045-20220925
hexagon              randconfig-r041-20220926
hexagon              randconfig-r045-20220926
hexagon              randconfig-r041-20220925
riscv                randconfig-r042-20220926
s390                 randconfig-r044-20220926
i386                 randconfig-a011-20220926
i386                 randconfig-a015-20220926
x86_64                        randconfig-a012
i386                 randconfig-a014-20220926
i386                 randconfig-a013-20220926
i386                 randconfig-a016-20220926
x86_64                        randconfig-a014
i386                 randconfig-a012-20220926
x86_64                        randconfig-a016

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-10-01 10:44 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=63381a1d.1RMK5Xirt7dxFPZ9%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).