From: kernel test robot <lkp@intel.com>
To: Nava kishore Manne <nava.manne@xilinx.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [PATCH v5 1/5] fpga: zynq: Fix incorrect variable type
Date: Sat, 23 Apr 2022 18:21:24 +0800 [thread overview]
Message-ID: <202204231832.eX31L2dR-lkp@intel.com> (raw)
In-Reply-To: <20220421044744.3777983-2-nava.manne@xilinx.com>
Hi Nava,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.18-rc3]
[cannot apply to xilinx-xlnx/master next-20220422]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/intel-lab-lkp/linux/commits/Nava-kishore-Manne/fpga-zynq-Fix-incorrect-variable-type/20220421-135249
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git b253435746d9a4a701b5f09211b9c14d3370d0da
config: mips-randconfig-r005-20220422 (https://download.01.org/0day-ci/archive/20220423/202204231832.eX31L2dR-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 5bd87350a5ae429baf8f373cb226a57b62f87280)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install mips cross compiling tool for clang build
# apt-get install binutils-mips-linux-gnu
# https://github.com/intel-lab-lkp/linux/commit/14e1fd8955f47ca1dbb9b58fee3b0b94429fc5d5
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Nava-kishore-Manne/fpga-zynq-Fix-incorrect-variable-type/20220421-135249
git checkout 14e1fd8955f47ca1dbb9b58fee3b0b94429fc5d5
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash drivers/fpga/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/fpga/zynq-fpga.c:246:14: warning: result of comparison of constant 170 with expression of type 'const char' is always false [-Wtautological-constant-out-of-range-compare]
buf[3] == 0xaa)
~~~~~~ ^ ~~~~
drivers/fpga/zynq-fpga.c:245:50: warning: result of comparison of constant 153 with expression of type 'const char' is always false [-Wtautological-constant-out-of-range-compare]
if (buf[0] == 0x66 && buf[1] == 0x55 && buf[2] == 0x99 &&
~~~~~~ ^ ~~~~
2 warnings generated.
vim +246 drivers/fpga/zynq-fpga.c
37784706bf9e3b Moritz Fischer 2015-10-16 237
b496df86ac1bbe Jason Gunthorpe 2017-02-01 238 /* Sanity check the proposed bitstream. It must start with the sync word in
b496df86ac1bbe Jason Gunthorpe 2017-02-01 239 * the correct byte order, and be dword aligned. The input is a Xilinx .bin
b496df86ac1bbe Jason Gunthorpe 2017-02-01 240 * file with every 32 bit quantity swapped.
b496df86ac1bbe Jason Gunthorpe 2017-02-01 241 */
14e1fd8955f47c Nava kishore Manne 2022-04-21 242 static bool zynq_fpga_has_sync(const char *buf, size_t count)
b496df86ac1bbe Jason Gunthorpe 2017-02-01 243 {
b496df86ac1bbe Jason Gunthorpe 2017-02-01 244 for (; count >= 4; buf += 4, count -= 4)
b496df86ac1bbe Jason Gunthorpe 2017-02-01 245 if (buf[0] == 0x66 && buf[1] == 0x55 && buf[2] == 0x99 &&
b496df86ac1bbe Jason Gunthorpe 2017-02-01 @246 buf[3] == 0xaa)
b496df86ac1bbe Jason Gunthorpe 2017-02-01 247 return true;
b496df86ac1bbe Jason Gunthorpe 2017-02-01 248 return false;
b496df86ac1bbe Jason Gunthorpe 2017-02-01 249 }
b496df86ac1bbe Jason Gunthorpe 2017-02-01 250
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-04-23 10:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 4:47 [PATCH v5 0/5]fpga: fix for coding style and kernel-doc issues Nava kishore Manne
2022-04-21 4:47 ` Nava kishore Manne
2022-04-21 4:47 ` [PATCH v5 1/5] fpga: zynq: Fix incorrect variable type Nava kishore Manne
2022-04-21 4:47 ` Nava kishore Manne
2022-04-21 15:52 ` Xu Yilun
2022-04-21 15:52 ` Xu Yilun
2022-04-23 10:21 ` kernel test robot [this message]
2022-04-21 4:47 ` [PATCH v5 2/5] fpga: fix for coding style issues Nava kishore Manne
2022-04-21 4:47 ` Nava kishore Manne
2022-04-21 15:34 ` Xu Yilun
2022-04-21 15:34 ` Xu Yilun
2022-04-22 3:38 ` Nava kishore Manne
2022-04-22 3:38 ` Nava kishore Manne
2022-04-21 4:47 ` [PATCH v5 3/5] fpga: fpga-mgr: fix kernel-doc warnings Nava kishore Manne
2022-04-21 4:47 ` Nava kishore Manne
2022-04-21 4:47 ` [PATCH v5 4/5] fpga: Use tab instead of space indentation Nava kishore Manne
2022-04-21 4:47 ` Nava kishore Manne
2022-04-21 4:47 ` [PATCH v5 5/5] fpga: fpga-region: fix kernel-doc formatting issues Nava kishore Manne
2022-04-21 4:47 ` Nava kishore Manne
2022-04-21 14:25 ` [PATCH v5 0/5]fpga: fix for coding style and kernel-doc issues Moritz Fischer
2022-04-21 14:25 ` Moritz Fischer
2022-04-21 15:55 ` Xu Yilun
2022-04-21 15:55 ` Xu Yilun
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=202204231832.eX31L2dR-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@lists.linux.dev \
--cc=nava.manne@xilinx.com \
/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.