linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Srinivasan Raju <srini.raju@purelifi.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Kalle Valo <kvalo@kernel.org>
Subject: [linux-next:master 5852/7483] drivers/net/wireless/purelifi/plfxlc/chip.c:33:14: sparse: sparse: cast to restricted __le16
Date: Fri, 29 Apr 2022 06:12:58 +0800	[thread overview]
Message-ID: <202204290641.UGDfvg2b-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   bdc61aad77faf67187525028f1f355eff3849f22
commit: 68d57a07bfe5bb29b80cd8b8fa24c9d1ea104124 [5852/7483] wireless: add plfxlc driver for pureLiFi X, XL, XC devices
config: alpha-allmodconfig (https://download.01.org/0day-ci/archive/20220429/202204290641.UGDfvg2b-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 11.3.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=68d57a07bfe5bb29b80cd8b8fa24c9d1ea104124
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 68d57a07bfe5bb29b80cd8b8fa24c9d1ea104124
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=alpha SHELL=/bin/bash drivers/net/wireless/purelifi/plfxlc/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)
>> drivers/net/wireless/purelifi/plfxlc/chip.c:33:14: sparse: sparse: cast to restricted __le16
>> drivers/net/wireless/purelifi/plfxlc/chip.c:36:31: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned short [usertype] beacon_interval @@     got restricted __le16 [usertype] @@
   drivers/net/wireless/purelifi/plfxlc/chip.c:36:31: sparse:     expected unsigned short [usertype] beacon_interval
   drivers/net/wireless/purelifi/plfxlc/chip.c:36:31: sparse:     got restricted __le16 [usertype]

vim +33 drivers/net/wireless/purelifi/plfxlc/chip.c

    27	
    28	int plfxlc_set_beacon_interval(struct plfxlc_chip *chip, u16 interval,
    29				       u8 dtim_period, int type)
    30	{
    31		if (!interval ||
    32		    (chip->beacon_set &&
  > 33		     le16_to_cpu(chip->beacon_interval) == interval))
    34			return 0;
    35	
  > 36		chip->beacon_interval = cpu_to_le16(interval);
    37		chip->beacon_set = true;
    38		return plfxlc_usb_wreq(chip->usb.ez_usb,
    39				       &chip->beacon_interval,
    40				       sizeof(chip->beacon_interval),
    41				       USB_REQ_BEACON_INTERVAL_WR);
    42	}
    43	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp


             reply	other threads:[~2022-04-28 22:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 22:12 kernel test robot [this message]
2022-04-29  5:49 ` Kalle Valo

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=202204290641.UGDfvg2b-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kvalo@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=srini.raju@purelifi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox