From: kernel test robot <lkp@intel.com>
To: Intel Wired LAN <intel-wired-lan@lists.osuosl.org>
Subject: [Intel-wired-lan] [tnguy-next-queue:10GbE] BUILD SUCCESS df58ee7d8faf353ebf5d4703c35fcf3e578e9b1b
Date: Mon, 17 Nov 2025 03:38:05 +0800 [thread overview]
Message-ID: <202511170358.bR2HJASB-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git 10GbE
branch HEAD: df58ee7d8faf353ebf5d4703c35fcf3e578e9b1b Merge branch 'net-phy-mscc-add-support-for-phy-led-control'
elapsed time: 3907m
configs tested: 71
configs skipped: 0
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc-15.1.0
arc allnoconfig gcc-15.1.0
arc randconfig-001-20251115 gcc-13.4.0
arc randconfig-002-20251115 gcc-11.5.0
arm allnoconfig clang-22
arm randconfig-001-20251115 clang-22
arm randconfig-002-20251115 gcc-8.5.0
arm randconfig-003-20251115 gcc-10.5.0
arm randconfig-004-20251115 clang-22
arm64 allnoconfig gcc-15.1.0
arm64 randconfig-001-20251116 gcc-12.5.0
arm64 randconfig-002-20251116 gcc-10.5.0
arm64 randconfig-003-20251116 clang-22
arm64 randconfig-004-20251116 gcc-8.5.0
csky allnoconfig gcc-15.1.0
csky randconfig-001-20251116 gcc-12.5.0
csky randconfig-002-20251116 gcc-15.1.0
hexagon allnoconfig clang-22
hexagon randconfig-001-20251116 clang-22
hexagon randconfig-002-20251116 clang-17
i386 allnoconfig gcc-14
loongarch allnoconfig clang-22
loongarch randconfig-001-20251116 gcc-15.1.0
loongarch randconfig-002-20251116 clang-22
m68k allnoconfig gcc-15.1.0
microblaze allnoconfig gcc-15.1.0
mips allnoconfig gcc-15.1.0
nios2 allnoconfig gcc-11.5.0
nios2 randconfig-001-20251116 gcc-11.5.0
nios2 randconfig-002-20251116 gcc-11.5.0
openrisc allnoconfig gcc-15.1.0
parisc allnoconfig gcc-15.1.0
parisc randconfig-001-20251115 gcc-8.5.0
parisc randconfig-001-20251116 gcc-12.5.0
parisc randconfig-002-20251115 gcc-8.5.0
parisc randconfig-002-20251116 gcc-14.3.0
powerpc allnoconfig gcc-15.1.0
powerpc randconfig-001-20251115 clang-19
powerpc randconfig-001-20251116 gcc-10.5.0
powerpc randconfig-002-20251115 gcc-8.5.0
powerpc randconfig-002-20251116 clang-22
powerpc64 randconfig-001-20251115 gcc-11.5.0
powerpc64 randconfig-001-20251116 clang-22
powerpc64 randconfig-002-20251115 gcc-14.3.0
powerpc64 randconfig-002-20251116 gcc-10.5.0
riscv allnoconfig gcc-15.1.0
riscv randconfig-001-20251115 clang-22
riscv randconfig-002-20251115 gcc-8.5.0
s390 allnoconfig clang-22
s390 randconfig-001-20251115 clang-17
s390 randconfig-002-20251115 gcc-8.5.0
sh allnoconfig gcc-15.1.0
sh randconfig-001-20251115 gcc-12.5.0
sh randconfig-002-20251115 gcc-15.1.0
sparc allnoconfig gcc-15.1.0
um allnoconfig clang-22
x86_64 allnoconfig clang-20
x86_64 buildonly-randconfig-001-20251116 clang-20
x86_64 buildonly-randconfig-002-20251116 clang-20
x86_64 buildonly-randconfig-003-20251116 clang-20
x86_64 buildonly-randconfig-004-20251116 gcc-13
x86_64 buildonly-randconfig-005-20251116 clang-20
x86_64 buildonly-randconfig-006-20251116 clang-20
x86_64 kexec clang-20
x86_64 rhel-9.4 clang-20
x86_64 rhel-9.4-bpf gcc-14
x86_64 rhel-9.4-func clang-20
x86_64 rhel-9.4-kselftests clang-20
x86_64 rhel-9.4-kunit gcc-14
x86_64 rhel-9.4-ltp gcc-14
xtensa allnoconfig gcc-15.1.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-16 19:38 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=202511170358.bR2HJASB-lkp@intel.com \
--to=lkp@intel.com \
--cc=intel-wired-lan@lists.osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.