From: kernel test robot <lkp@intel.com>
To: Deepanshu Kartikey <kartikey406@gmail.com>, gregkh@linuxfoundation.org
Cc: oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Deepanshu Kartikey <kartikey406@gmail.com>
Subject: Re: [PATCH] staging: fbtft: fbtft-bus.c added params
Date: Sun, 9 Apr 2023 01:26:13 +0800 [thread overview]
Message-ID: <202304090139.b8XZpHpu-lkp@intel.com> (raw)
In-Reply-To: <20230408081817.81562-1-kartikey406@gmail.com>
Hi Deepanshu,
kernel test robot noticed the following build warnings:
[auto build test WARNING on staging/staging-testing]
url: https://github.com/intel-lab-lkp/linux/commits/Deepanshu-Kartikey/staging-fbtft-fbtft-bus-c-added-params/20230408-161947
patch link: https://lore.kernel.org/r/20230408081817.81562-1-kartikey406%40gmail.com
patch subject: [PATCH] staging: fbtft: fbtft-bus.c added params
config: i386-randconfig-s001-20230403 (https://download.01.org/0day-ci/archive/20230409/202304090139.b8XZpHpu-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://github.com/intel-lab-lkp/linux/commit/038bedbb2c34ffc5e5ce77d5f49811778be8d631
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Deepanshu-Kartikey/staging-fbtft-fbtft-bus-c-added-params/20230408-161947
git checkout 038bedbb2c34ffc5e5ce77d5f49811778be8d631
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 olddefconfig
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/staging/fbtft/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304090139.b8XZpHpu-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/staging/fbtft/fbtft-bus.c:65:1: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned char [usertype] @@ got restricted __be16 [usertype] @@
drivers/staging/fbtft/fbtft-bus.c:65:1: sparse: expected unsigned char [usertype]
drivers/staging/fbtft/fbtft-bus.c:65:1: sparse: got restricted __be16 [usertype]
>> drivers/staging/fbtft/fbtft-bus.c:65:1: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned char [usertype] @@ got restricted __be16 [usertype] @@
drivers/staging/fbtft/fbtft-bus.c:65:1: sparse: expected unsigned char [usertype]
drivers/staging/fbtft/fbtft-bus.c:65:1: sparse: got restricted __be16 [usertype]
>> drivers/staging/fbtft/fbtft-bus.c:65:1: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned char [usertype] @@ got restricted __be16 [usertype] @@
drivers/staging/fbtft/fbtft-bus.c:65:1: sparse: expected unsigned char [usertype]
drivers/staging/fbtft/fbtft-bus.c:65:1: sparse: got restricted __be16 [usertype]
drivers/staging/fbtft/fbtft-bus.c:67:1: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned short [usertype] @@ got restricted __be16 [usertype] @@
drivers/staging/fbtft/fbtft-bus.c:67:1: sparse: expected unsigned short [usertype]
drivers/staging/fbtft/fbtft-bus.c:67:1: sparse: got restricted __be16 [usertype]
drivers/staging/fbtft/fbtft-bus.c:67:1: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned short [usertype] @@ got restricted __be16 [usertype] @@
drivers/staging/fbtft/fbtft-bus.c:67:1: sparse: expected unsigned short [usertype]
drivers/staging/fbtft/fbtft-bus.c:67:1: sparse: got restricted __be16 [usertype]
drivers/staging/fbtft/fbtft-bus.c:67:1: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned short [usertype] @@ got restricted __be16 [usertype] @@
drivers/staging/fbtft/fbtft-bus.c:67:1: sparse: expected unsigned short [usertype]
drivers/staging/fbtft/fbtft-bus.c:67:1: sparse: got restricted __be16 [usertype]
vim +65 drivers/staging/fbtft/fbtft-bus.c
64
> 65 define_fbtft_write_reg(fbtft_write_reg8_bus8, u8, u8, cpu_to_be16);
66 define_fbtft_write_reg(fbtft_write_reg16_bus8, __be16, u16, cpu_to_be16);
67 define_fbtft_write_reg(fbtft_write_reg16_bus16, u16, u16, cpu_to_be16);
68
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
prev parent reply other threads:[~2023-04-08 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 8:18 [PATCH] staging: fbtft: fbtft-bus.c added params Deepanshu Kartikey
2023-04-08 8:22 ` Greg KH
2023-04-08 17:26 ` kernel test robot [this message]
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=202304090139.b8XZpHpu-lkp@intel.com \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=kartikey406@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@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;
as well as URLs for NNTP newsgroup(s).