From: kernel test robot <lkp@intel.com>
To: Tejun Heo <tj@kernel.org>
Cc: cgroups@vger.kernel.org
Subject: [tj-cgroup:for-next] BUILD SUCCESS d7c1439faed666068a8bac8d3de2ae29c5f9f722
Date: Thu, 05 Jun 2025 03:34:11 +0800 [thread overview]
Message-ID: <202506050301.68crfs9e-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-next
branch HEAD: d7c1439faed666068a8bac8d3de2ae29c5f9f722 Merge branch 'for-6.17' into for-next
elapsed time: 1448m
configs tested: 34
configs skipped: 1
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allyesconfig gcc-15.1.0
arc allmodconfig gcc-15.1.0
arc allyesconfig gcc-15.1.0
arm allmodconfig gcc-15.1.0
arm allyesconfig gcc-15.1.0
arm64 allmodconfig clang-19
hexagon allmodconfig clang-17
hexagon allyesconfig clang-21
i386 allmodconfig gcc-12
i386 allnoconfig gcc-12
i386 allyesconfig gcc-12
i386 defconfig clang-20
loongarch allmodconfig gcc-15.1.0
m68k allmodconfig gcc-15.1.0
m68k allyesconfig gcc-15.1.0
microblaze allmodconfig gcc-15.1.0
microblaze allyesconfig gcc-15.1.0
openrisc allyesconfig gcc-15.1.0
parisc allmodconfig gcc-15.1.0
parisc allyesconfig gcc-15.1.0
powerpc allmodconfig gcc-15.1.0
powerpc allyesconfig clang-21
riscv allmodconfig clang-21
s390 allmodconfig clang-18
s390 allyesconfig gcc-15.1.0
sh allmodconfig gcc-15.1.0
sh allyesconfig gcc-15.1.0
sparc allmodconfig gcc-15.1.0
um allmodconfig clang-19
um allyesconfig gcc-12
x86_64 allnoconfig clang-20
x86_64 allyesconfig clang-20
x86_64 defconfig gcc-11
x86_64 rhel-9.4-rust clang-18
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-06-04 19:34 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=202506050301.68crfs9e-lkp@intel.com \
--to=lkp@intel.com \
--cc=cgroups@vger.kernel.org \
--cc=tj@kernel.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 NNTP newsgroup(s).