From: kernel test robot <lkp@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-acpi@vger.kernel.org, devel@acpica.org, linux-pm@vger.kernel.org
Subject: [rafael-pm:bleeding-edge] BUILD SUCCESS 413e2254b7a67f21e05791073f95ad41e0a54593
Date: Sat, 17 Aug 2024 19:04:20 +0800 [thread overview]
Message-ID: <202408171917.sr18nka7-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
branch HEAD: 413e2254b7a67f21e05791073f95ad41e0a54593 Merge branch 'thermal-core-testing' into bleeding-edge
elapsed time: 1351m
configs tested: 75
configs skipped: 1
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allyesconfig gcc-13.3.0
arc allmodconfig gcc-13.2.0
arc allyesconfig gcc-13.2.0
arc axs103_smp_defconfig gcc-13.2.0
arm allmodconfig gcc-14.1.0
arm allyesconfig gcc-14.1.0
arm realview_defconfig clang-20
arm sama7_defconfig clang-20
arm spear13xx_defconfig gcc-14.1.0
arm stm32_defconfig gcc-14.1.0
arm64 allmodconfig clang-20
hexagon allmodconfig clang-20
hexagon allyesconfig clang-20
i386 allmodconfig gcc-12
i386 allnoconfig gcc-12
i386 allyesconfig gcc-12
i386 buildonly-randconfig-001-20240817 gcc-12
i386 buildonly-randconfig-002-20240817 gcc-12
i386 buildonly-randconfig-003-20240817 clang-18
i386 buildonly-randconfig-004-20240817 gcc-12
i386 buildonly-randconfig-005-20240817 clang-18
i386 buildonly-randconfig-006-20240817 clang-18
i386 defconfig clang-18
i386 randconfig-001-20240817 gcc-12
i386 randconfig-002-20240817 gcc-12
i386 randconfig-003-20240817 gcc-12
i386 randconfig-004-20240817 clang-18
i386 randconfig-005-20240817 gcc-12
i386 randconfig-006-20240817 clang-18
i386 randconfig-011-20240817 gcc-12
i386 randconfig-012-20240817 clang-18
i386 randconfig-013-20240817 gcc-12
i386 randconfig-014-20240817 gcc-12
i386 randconfig-015-20240817 gcc-12
i386 randconfig-016-20240817 clang-18
loongarch allmodconfig gcc-14.1.0
m68k allmodconfig gcc-14.1.0
m68k allyesconfig gcc-14.1.0
microblaze allmodconfig gcc-14.1.0
microblaze allyesconfig gcc-14.1.0
openrisc allnoconfig gcc-14.1.0
openrisc allyesconfig gcc-14.1.0
parisc allmodconfig gcc-14.1.0
parisc allnoconfig gcc-14.1.0
parisc allyesconfig gcc-14.1.0
parisc generic-32bit_defconfig gcc-14.1.0
parisc generic-64bit_defconfig gcc-14.1.0
powerpc allmodconfig gcc-14.1.0
powerpc allnoconfig gcc-14.1.0
powerpc allyesconfig clang-20
powerpc icon_defconfig gcc-14.1.0
powerpc linkstation_defconfig clang-20
powerpc mpc8313_rdb_defconfig gcc-14.1.0
powerpc pcm030_defconfig clang-20
powerpc tqm8540_defconfig gcc-14.1.0
riscv alldefconfig gcc-14.1.0
riscv allmodconfig clang-20
riscv allnoconfig gcc-14.1.0
riscv allyesconfig clang-20
riscv defconfig clang-20
s390 allmodconfig clang-20
s390 allnoconfig clang-20
s390 allyesconfig gcc-14.1.0
sh allmodconfig gcc-14.1.0
sh allyesconfig gcc-14.1.0
sh shmin_defconfig gcc-14.1.0
sparc allmodconfig gcc-14.1.0
um allmodconfig clang-20
um allnoconfig clang-17
um allyesconfig gcc-12
x86_64 allnoconfig clang-18
x86_64 allyesconfig clang-18
x86_64 defconfig gcc-11
x86_64 rhel-8.3-rust clang-18
xtensa nommu_kc705_defconfig gcc-14.1.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-08-17 11:04 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=202408171917.sr18nka7-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