From: kernel test robot <lkp@intel.com>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org
Subject: [linux-nvme:nvme-6.8] BUILD SUCCESS 15ade5bfa5abf0e02249239db91d5438fa796d18
Date: Fri, 26 Jan 2024 02:21:35 +0800 [thread overview]
Message-ID: <202401260233.RuP9BmiZ-lkp@intel.com> (raw)
tree/branch: git://git.infradead.org/nvme.git nvme-6.8
branch HEAD: 15ade5bfa5abf0e02249239db91d5438fa796d18 nvme-rdma: Fix transfer length when write_generate/read_verify are 0
elapsed time: 1578m
configs tested: 77
configs skipped: 1
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc
alpha defconfig gcc
arc allnoconfig gcc
arc randconfig-001-20240125 gcc
arc randconfig-002-20240125 gcc
arm randconfig-001-20240125 gcc
arm randconfig-002-20240125 gcc
arm randconfig-003-20240125 gcc
arm randconfig-004-20240125 gcc
arm64 randconfig-001-20240125 gcc
arm64 randconfig-002-20240125 gcc
arm64 randconfig-003-20240125 gcc
arm64 randconfig-004-20240125 gcc
csky randconfig-001-20240125 gcc
csky randconfig-002-20240125 gcc
i386 allmodconfig clang
i386 allnoconfig clang
i386 allyesconfig clang
i386 buildonly-randconfig-001-20240125 gcc
i386 buildonly-randconfig-002-20240125 gcc
i386 buildonly-randconfig-003-20240125 gcc
i386 buildonly-randconfig-004-20240125 gcc
i386 buildonly-randconfig-005-20240125 gcc
i386 buildonly-randconfig-006-20240125 gcc
i386 defconfig gcc
i386 randconfig-001-20240125 gcc
i386 randconfig-002-20240125 gcc
i386 randconfig-003-20240125 gcc
i386 randconfig-004-20240125 gcc
i386 randconfig-005-20240125 gcc
i386 randconfig-006-20240125 gcc
i386 randconfig-011-20240125 clang
i386 randconfig-012-20240125 clang
i386 randconfig-013-20240125 clang
i386 randconfig-014-20240125 clang
i386 randconfig-015-20240125 clang
i386 randconfig-016-20240125 clang
loongarch allmodconfig gcc
loongarch randconfig-001-20240125 gcc
m68k allmodconfig gcc
m68k allyesconfig gcc
microblaze allmodconfig gcc
microblaze allyesconfig gcc
mips allyesconfig gcc
nios2 allmodconfig gcc
nios2 allyesconfig gcc
openrisc allnoconfig gcc
openrisc defconfig gcc
parisc allnoconfig gcc
parisc defconfig gcc
parisc64 defconfig gcc
powerpc allnoconfig gcc
riscv allnoconfig clang
riscv defconfig gcc
s390 allmodconfig gcc
s390 allnoconfig gcc
s390 allyesconfig gcc
s390 defconfig gcc
sh allmodconfig gcc
sh allnoconfig gcc
sh allyesconfig gcc
sh defconfig gcc
sparc allmodconfig gcc
sparc allnoconfig gcc
sparc defconfig gcc
sparc64 allmodconfig gcc
sparc64 allyesconfig gcc
sparc64 defconfig gcc
um allnoconfig clang
um defconfig gcc
um i386_defconfig gcc
um x86_64_defconfig gcc
x86_64 allnoconfig gcc
x86_64 allyesconfig clang
x86_64 defconfig gcc
x86_64 rhel-8.3-rust clang
xtensa allnoconfig gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-25 18:22 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=202401260233.RuP9BmiZ-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 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.