From: kernel test robot <lkp@intel.com>
To: Intel Wired LAN <intel-wired-lan@lists.osuosl.org>
Subject: [Intel-wired-lan] [tnguy-net-queue:200GbE] BUILD SUCCESS 5442a9da69789741bfda39f34ee7f69552bf0c56
Date: Wed, 19 Nov 2025 01:55:19 +0800 [thread overview]
Message-ID: <202511190114.7zCjxsRM-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue.git 200GbE
branch HEAD: 5442a9da69789741bfda39f34ee7f69552bf0c56 veth: more robust handing of race to avoid txq getting stuck
elapsed time: 5223m
configs tested: 78
configs skipped: 2
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-20251118 gcc-14.3.0
arc randconfig-002-20251118 gcc-15.1.0
arm allnoconfig clang-22
arm randconfig-001-20251118 gcc-8.5.0
arm randconfig-002-20251118 gcc-10.5.0
arm randconfig-003-20251118 clang-22
arm randconfig-004-20251118 clang-22
arm versatile_defconfig gcc-15.1.0
arm64 allnoconfig gcc-15.1.0
arm64 randconfig-001-20251118 clang-20
arm64 randconfig-002-20251118 clang-22
arm64 randconfig-003-20251118 clang-19
arm64 randconfig-004-20251118 clang-17
csky allnoconfig gcc-15.1.0
csky randconfig-001-20251118 gcc-10.5.0
csky randconfig-002-20251118 gcc-15.1.0
hexagon allnoconfig clang-22
i386 allnoconfig gcc-14
i386 randconfig-001-20251119 clang-20
i386 randconfig-002-20251119 clang-20
i386 randconfig-003-20251119 clang-20
i386 randconfig-004-20251119 clang-20
i386 randconfig-005-20251119 clang-20
i386 randconfig-006-20251119 gcc-14
i386 randconfig-007-20251119 gcc-14
loongarch allnoconfig clang-22
m68k allnoconfig gcc-15.1.0
microblaze allnoconfig gcc-15.1.0
mips allnoconfig gcc-15.1.0
mips bcm47xx_defconfig clang-18
mips gcw0_defconfig clang-22
nios2 allnoconfig gcc-11.5.0
openrisc allnoconfig gcc-15.1.0
openrisc defconfig gcc-15.1.0
parisc allnoconfig gcc-15.1.0
parisc defconfig gcc-15.1.0
parisc randconfig-001-20251118 gcc-14.3.0
parisc randconfig-002-20251118 gcc-12.5.0
powerpc allnoconfig gcc-15.1.0
powerpc randconfig-001-20251118 clang-22
powerpc randconfig-002-20251118 clang-22
powerpc wii_defconfig gcc-15.1.0
powerpc64 randconfig-001-20251118 gcc-13.4.0
powerpc64 randconfig-002-20251118 gcc-8.5.0
riscv allnoconfig gcc-15.1.0
riscv defconfig clang-22
s390 allnoconfig clang-22
s390 defconfig clang-22
sh allnoconfig gcc-15.1.0
sh defconfig gcc-15.1.0
sh rts7751r2dplus_defconfig gcc-15.1.0
sh se7750_defconfig gcc-15.1.0
sh sh7710voipgw_defconfig gcc-15.1.0
sparc allnoconfig gcc-15.1.0
sparc defconfig gcc-15.1.0
sparc64 defconfig clang-20
um allnoconfig clang-22
um defconfig clang-22
um i386_defconfig gcc-14
um x86_64_defconfig clang-22
x86_64 allnoconfig clang-20
x86_64 defconfig gcc-14
x86_64 kexec clang-20
x86_64 randconfig-071-20251119 gcc-14
x86_64 randconfig-072-20251119 clang-20
x86_64 randconfig-073-20251119 gcc-12
x86_64 randconfig-074-20251119 clang-20
x86_64 randconfig-075-20251119 clang-20
x86_64 randconfig-076-20251119 gcc-14
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-18 17:56 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=202511190114.7zCjxsRM-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 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).