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:fixes] BUILD SUCCESS e2046b72e9797df8569a79b839b6bfaedd6377fe
Date: Thu, 16 Jan 2025 05:24:28 +0800 [thread overview]
Message-ID: <202501160522.9WTK2Qg3-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git fixes
branch HEAD: e2046b72e9797df8569a79b839b6bfaedd6377fe Merge branch 'pm-cpufreq-fixes' into fixes
elapsed time: 1455m
configs tested: 64
configs skipped: 9
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc-14.2.0
arc randconfig-001-20250115 gcc-13.2.0
arm allnoconfig clang-17
arm64 allnoconfig gcc-14.2.0
arm64 randconfig-002-20250115 gcc-14.2.0
csky randconfig-001-20250115 gcc-14.2.0
csky randconfig-002-20250115 gcc-14.2.0
hexagon randconfig-001-20250115 clang-20
hexagon randconfig-002-20250115 clang-19
i386 buildonly-randconfig-001-20250115 clang-19
i386 buildonly-randconfig-002-20250115 gcc-12
i386 buildonly-randconfig-003-20250115 gcc-12
i386 buildonly-randconfig-004-20250115 gcc-12
i386 buildonly-randconfig-005-20250115 gcc-12
i386 buildonly-randconfig-006-20250115 gcc-12
loongarch randconfig-001-20250115 gcc-14.2.0
loongarch randconfig-002-20250115 gcc-14.2.0
m68k allnoconfig gcc-14.2.0
microblaze allnoconfig gcc-14.2.0
mips allnoconfig gcc-14.2.0
nios2 allnoconfig gcc-14.2.0
nios2 randconfig-001-20250115 gcc-14.2.0
nios2 randconfig-002-20250115 gcc-14.2.0
openrisc allnoconfig gcc-14.2.0
parisc allnoconfig gcc-14.2.0
parisc randconfig-001-20250115 gcc-14.2.0
parisc randconfig-002-20250115 gcc-14.2.0
powerpc allnoconfig gcc-14.2.0
powerpc randconfig-001-20250115 gcc-14.2.0
powerpc randconfig-002-20250115 gcc-14.2.0
powerpc randconfig-003-20250115 gcc-14.2.0
powerpc64 randconfig-001-20250115 gcc-14.2.0
powerpc64 randconfig-002-20250115 gcc-14.2.0
powerpc64 randconfig-003-20250115 clang-18
riscv allnoconfig gcc-14.2.0
riscv randconfig-001-20250115 gcc-14.2.0
riscv randconfig-002-20250115 clang-16
s390 allmodconfig clang-19
s390 allnoconfig clang-20
s390 allyesconfig gcc-14.2.0
s390 randconfig-001-20250115 clang-20
s390 randconfig-002-20250115 clang-15
sh allmodconfig gcc-14.2.0
sh allnoconfig gcc-14.2.0
sh allyesconfig gcc-14.2.0
sh randconfig-001-20250115 gcc-14.2.0
sh randconfig-002-20250115 gcc-14.2.0
sparc allmodconfig gcc-14.2.0
sparc allnoconfig gcc-14.2.0
sparc randconfig-001-20250115 gcc-14.2.0
sparc randconfig-002-20250115 gcc-14.2.0
sparc64 randconfig-001-20250115 gcc-14.2.0
sparc64 randconfig-002-20250115 gcc-14.2.0
um allnoconfig clang-18
um randconfig-001-20250115 clang-18
um randconfig-002-20250115 gcc-12
x86_64 allnoconfig clang-19
x86_64 buildonly-randconfig-001-20250115 gcc-12
x86_64 buildonly-randconfig-002-20250115 gcc-12
x86_64 buildonly-randconfig-006-20250115 clang-19
x86_64 defconfig gcc-11
xtensa allnoconfig gcc-14.2.0
xtensa randconfig-001-20250115 gcc-14.2.0
xtensa randconfig-002-20250115 gcc-14.2.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-15 21:25 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=202501160522.9WTK2Qg3-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