From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-nvme@lists.infradead.org
Subject: [linux-nvme:nvme-5.19] BUILD SUCCESS WITH WARNING 4db675888cdb7b24812e289d7f90e7928dd400a3
Date: Thu, 30 Jun 2022 13:58:42 +0800 [thread overview]
Message-ID: <62bd3b92.UluA72FI79OFZKgS%lkp@intel.com> (raw)
tree/branch: git://git.infradead.org/nvme.git nvme-5.19
branch HEAD: 4db675888cdb7b24812e289d7f90e7928dd400a3 nvmet: add a clear_ids attribute for passthru targets
Warning: (recently discovered and may have been fixed)
drivers/nvme/target/passthru.c:54:16: warning: variable 'csi_seen' is used uninitialized whenever 'for' loop exits because its condition is false [-Wsometimes-uninitialized]
drivers/nvme/target/passthru.c:57:7: warning: variable 'csi_seen' is used uninitialized whenever 'if' condition is true [-Wsometimes-uninitialized]
Warning ids grouped by kconfigs:
clang_recent_errors
|-- arm-randconfig-r015-20220629
| |-- drivers-nvme-target-passthru.c:warning:variable-csi_seen-is-used-uninitialized-whenever-for-loop-exits-because-its-condition-is-false
| `-- drivers-nvme-target-passthru.c:warning:variable-csi_seen-is-used-uninitialized-whenever-if-condition-is-true
`-- x86_64-randconfig-a014
|-- drivers-nvme-target-passthru.c:warning:variable-csi_seen-is-used-uninitialized-whenever-for-loop-exits-because-its-condition-is-false
`-- drivers-nvme-target-passthru.c:warning:variable-csi_seen-is-used-uninitialized-whenever-if-condition-is-true
elapsed time: 723m
configs tested: 52
configs skipped: 2
gcc tested configs:
arm defconfig
arm allyesconfig
arm64 allyesconfig
ia64 allmodconfig
mips allyesconfig
powerpc allmodconfig
powerpc allnoconfig
sh allmodconfig
i386 defconfig
i386 allyesconfig
arc allyesconfig
alpha allyesconfig
m68k allmodconfig
m68k allyesconfig
x86_64 randconfig-a004
x86_64 randconfig-a002
x86_64 randconfig-a006
i386 randconfig-a001
i386 randconfig-a003
i386 randconfig-a005
x86_64 randconfig-a013
x86_64 randconfig-a011
x86_64 randconfig-a015
i386 randconfig-a014
i386 randconfig-a012
i386 randconfig-a016
arc randconfig-r043-20220629
s390 randconfig-r044-20220629
riscv randconfig-r042-20220629
um i386_defconfig
um x86_64_defconfig
x86_64 rhel-8.3-kselftests
x86_64 rhel-8.3-func
x86_64 rhel-8.3-kunit
x86_64 rhel-8.3-syz
x86_64 defconfig
x86_64 allyesconfig
x86_64 rhel-8.3
clang tested configs:
x86_64 randconfig-a005
x86_64 randconfig-a001
x86_64 randconfig-a003
i386 randconfig-a002
i386 randconfig-a004
i386 randconfig-a006
x86_64 randconfig-a012
x86_64 randconfig-a014
x86_64 randconfig-a016
i386 randconfig-a013
i386 randconfig-a015
i386 randconfig-a011
hexagon randconfig-r041-20220629
hexagon randconfig-r045-20220629
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-06-30 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 5:58 kernel test robot [this message]
2022-06-30 6:24 ` [linux-nvme:nvme-5.19] BUILD SUCCESS WITH WARNING 4db675888cdb7b24812e289d7f90e7928dd400a3 Christoph Hellwig
2022-06-30 16:54 ` Alan Adamson
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=62bd3b92.UluA72FI79OFZKgS%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