From: kernel test robot <lkp@intel.com>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org
Subject: [linux-nvme:nvme-7.3] BUILD SUCCESS 9952f3882ecba709092379b71e02b09762b26f96
Date: Tue, 21 Jul 2026 06:02:49 +0800 [thread overview]
Message-ID: <202607210635.CmbtYpLH-lkp@intel.com> (raw)
tree/branch: git://git.infradead.org/nvme.git nvme-7.3
branch HEAD: 9952f3882ecba709092379b71e02b09762b26f96 nvme: fix cdev lifetime
elapsed time: 5778m
configs tested: 34
configs skipped: 0
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc-16.1.0
alpha allyesconfig gcc-16.1.0
alpha defconfig gcc-16.1.0
arc allmodconfig gcc-16.1.0
arc allyesconfig gcc-16.1.0
csky allmodconfig gcc-16.1.0
hexagon randconfig-001 clang-17
hexagon randconfig-001-20260717 clang-24
hexagon randconfig-002-20260717 clang-17
i386 allmodconfig gcc-14
loongarch defconfig clang-24
loongarch randconfig-001-20260717 gcc-16.1.0
loongarch randconfig-002-20260717 clang-24
nios2 allmodconfig gcc-11.5.0
nios2 allnoconfig gcc-11.5.0
nios2 randconfig-001-20260717 gcc-8.5.0
nios2 randconfig-002-20260717 gcc-8.5.0
parisc allmodconfig gcc-16.1.0
parisc allyesconfig gcc-16.1.0
sh defconfig gcc-16.1.0
x86_64 kexec clang-22
x86_64 randconfig-011-20260717 gcc-14
x86_64 randconfig-012-20260717 gcc-14
x86_64 randconfig-013-20260717 clang-22
x86_64 randconfig-014-20260717 gcc-12
x86_64 randconfig-015-20260717 gcc-14
x86_64 randconfig-016-20260717 gcc-14
x86_64 randconfig-071-20260717 gcc-14
x86_64 randconfig-072-20260717 gcc-14
x86_64 randconfig-073-20260717 gcc-14
x86_64 randconfig-074-20260717 gcc-12
x86_64 randconfig-075-20260717 gcc-14
x86_64 randconfig-076-20260717 clang-22
x86_64 rhel-9.4-bpf gcc-14
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-20 22:03 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=202607210635.CmbtYpLH-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.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