From: kernel test robot <lkp@intel.com>
To: Intel Wired LAN <intel-wired-lan@lists.osuosl.org>
Subject: [tnguy-net-queue:100GbE] BUILD SUCCESS 9ebbb58e13b4759605d0107ba8538409b9acbf4d
Date: Tue, 27 Oct 2026 08:28:51 +0800 [thread overview]
Message-ID: <202610270843.pjVbZwuK-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue.git 100GbE
branch HEAD: 9ebbb58e13b4759605d0107ba8538409b9acbf4d ice: don't clear in_use until HW clears ready bitmap
elapsed time: 3596m
configs tested: 79
configs skipped: 6
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc-16.2.0
alpha allyesconfig gcc-16.2.0
arc allmodconfig gcc-16.2.0
arc allnoconfig gcc-16.2.0
arc allyesconfig gcc-16.2.0
arm allnoconfig clang-17
arm allyesconfig gcc-16.2.0
arm64 allmodconfig clang-24
arm64 allnoconfig gcc-16.2.0
arm64 randconfig-1000-20261027 gcc-13.5.0
arm64 randconfig-1001-20261027 clang-17
arm64 randconfig-1002-20261027 gcc-8.5.0
arm64 randconfig-1003-20261027 gcc-8.5.0
csky allmodconfig gcc-16.2.0
csky allnoconfig gcc-16.2.0
csky randconfig-1000-20261027 gcc-16.2.0
csky randconfig-1001-20261027 gcc-16.2.0
hexagon allmodconfig clang-24
hexagon allnoconfig clang-24
hexagon randconfig-1000-20261027 clang-24
hexagon randconfig-1001-20261027 clang-24
i386 allnoconfig gcc-14
i386 buildonly-randconfig-1000-20261027 gcc-14
i386 buildonly-randconfig-1001-20261027 gcc-14
i386 buildonly-randconfig-1002-20261027 clang-22
i386 buildonly-randconfig-1003-20261027 gcc-14
i386 buildonly-randconfig-1004-20261027 clang-22
i386 buildonly-randconfig-1005-20261027 clang-22
loongarch allmodconfig clang-19
loongarch allnoconfig clang-20
loongarch randconfig-1000-20261027 gcc-13.5.0
loongarch randconfig-1001-20261027 gcc-15.3.0
m68k allmodconfig gcc-16.2.0
m68k allnoconfig gcc-16.2.0
m68k allyesconfig gcc-16.2.0
microblaze allnoconfig gcc-16.2.0
microblaze allyesconfig gcc-16.2.0
mips allmodconfig gcc-16.2.0
mips allnoconfig gcc-16.2.0
mips allyesconfig gcc-16.2.0
nios2 allmodconfig gcc-11.5.0
nios2 allnoconfig gcc-11.5.0
nios2 randconfig-1000-20261027 gcc-8.5.0
nios2 randconfig-1001-20261027 gcc-8.5.0
openrisc allmodconfig gcc-16.2.0
openrisc allnoconfig gcc-16.2.0
openrisc defconfig gcc-16.2.0
parisc allmodconfig gcc-16.2.0
parisc allnoconfig gcc-16.2.0
parisc allyesconfig gcc-16.2.0
parisc defconfig gcc-16.2.0
parisc randconfig-1000-20261027 gcc-12.5.0
parisc randconfig-1001-20261027 gcc-10.5.0
powerpc allmodconfig gcc-16.2.0
powerpc allnoconfig gcc-16.2.0
powerpc randconfig-1000-20261027 gcc-15.3.0
powerpc randconfig-1001-20261027 gcc-8.5.0
powerpc64 randconfig-1000-20261027 gcc-10.5.0
powerpc64 randconfig-1001-20261027 clang-22
riscv allmodconfig clang-24
riscv allnoconfig gcc-16.2.0
riscv allyesconfig clang-24
riscv defconfig clang-24
s390 allmodconfig clang-24
s390 allnoconfig clang-24
s390 allyesconfig gcc-16.2.0
s390 defconfig clang-18
sh allmodconfig gcc-16.2.0
sh allnoconfig gcc-16.2.0
sh allyesconfig gcc-16.2.0
sparc allnoconfig gcc-16.2.0
sparc defconfig gcc-16.2.0
sparc64 allmodconfig clang-20
um allmodconfig clang-17
um allnoconfig clang-17
um allyesconfig gcc-14
x86_64 allnoconfig clang-22
xtensa allnoconfig gcc-16.2.0
xtensa allyesconfig gcc-16.2.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-27 0:29 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=202610270843.pjVbZwuK-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