From: kernel test robot <lkp@intel.com>
To: Danielle Ratson <danieller@nvidia.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Ido Schimmel <idosch@nvidia.com>
Subject: [jpirko-mlxsw:combined_queue 8/9] net/ethtool/cmis_fw_update.c:240:23: warning: converting the enum constant to a boolean
Date: Mon, 22 Jan 2024 05:19:44 +0800 [thread overview]
Message-ID: <202401220520.5K1hLmww-lkp@intel.com> (raw)
tree: https://github.com/jpirko/linux_mlxsw combined_queue
head: 2d94043682e019700926235499d603818f42460a
commit: 828c7605e322a6ae571a754298dfe361741bdcf2 [8/9] ethtool: cmis_fw_update: add a layer for supporting firmware update using CDB
config: i386-randconfig-001-20240122 (https://download.01.org/0day-ci/archive/20240122/202401220520.5K1hLmww-lkp@intel.com/config)
compiler: ClangBuiltLinux clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240122/202401220520.5K1hLmww-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202401220520.5K1hLmww-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> net/ethtool/cmis_fw_update.c:240:23: warning: converting the enum constant to a boolean [-Wint-in-bool-context]
240 | (CMIS_MODULE_READY || CMIS_MODULE_LOW_PWR));
| ^
1 warning generated.
vim +240 net/ethtool/cmis_fw_update.c
236
237 static bool module_is_ready(u8 data)
238 {
239 return (((data >> 1) & 7) ==
> 240 (CMIS_MODULE_READY || CMIS_MODULE_LOW_PWR));
241 }
242
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-21 21:20 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=202401220520.5K1hLmww-lkp@intel.com \
--to=lkp@intel.com \
--cc=danieller@nvidia.com \
--cc=idosch@nvidia.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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