From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-nvme@lists.infradead.org
Subject: [linux-nvme:nvme-6.2] BUILD SUCCESS 524badb852865b36a334d12d5bf6090f4556a737
Date: Thu, 15 Dec 2022 05:02:47 +0800 [thread overview]
Message-ID: <639a39f7.vrqFapGWRO1RVsAw%lkp@intel.com> (raw)
tree/branch: git://git.infradead.org/nvme.git nvme-6.2
branch HEAD: 524badb852865b36a334d12d5bf6090f4556a737 nvme-pci: fix doorbell buffer value endianness
elapsed time: 724m
configs tested: 63
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
um i386_defconfig
um x86_64_defconfig
powerpc allnoconfig
sh allmodconfig
arc randconfig-r043-20221213
mips allyesconfig
i386 defconfig
powerpc allmodconfig
arm randconfig-r046-20221213
arc defconfig
x86_64 rhel-8.3-bpf
x86_64 randconfig-a004
s390 allmodconfig
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-rust
ia64 allmodconfig
x86_64 rhel-8.3-kunit
i386 randconfig-a001
alpha defconfig
x86_64 randconfig-a013
i386 randconfig-a003
x86_64 rhel-8.3-kvm
s390 allyesconfig
x86_64 randconfig-a002
s390 defconfig
x86_64 rhel-8.3-kselftests
x86_64 randconfig-a011
m68k allmodconfig
arm defconfig
alpha allyesconfig
m68k allyesconfig
x86_64 rhel-8.3-func
x86_64 randconfig-a015
arc allyesconfig
x86_64 randconfig-a006
x86_64 defconfig
i386 randconfig-a005
arm allyesconfig
arm64 allyesconfig
x86_64 rhel-8.3
i386 allyesconfig
x86_64 allyesconfig
i386 randconfig-a014
i386 randconfig-a012
i386 randconfig-a016
x86_64 allnoconfig
clang tested configs:
hexagon randconfig-r041-20221213
hexagon randconfig-r045-20221213
riscv randconfig-r042-20221213
i386 randconfig-a002
s390 randconfig-r044-20221213
i386 randconfig-a004
x86_64 randconfig-a012
x86_64 randconfig-a005
x86_64 randconfig-a001
x86_64 randconfig-a003
x86_64 randconfig-a014
x86_64 randconfig-a016
i386 randconfig-a006
i386 randconfig-a013
i386 randconfig-a011
i386 randconfig-a015
x86_64 randconfig-k001
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-12-14 21: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=639a39f7.vrqFapGWRO1RVsAw%lkp@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--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