linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Loic Poulain <loic.poulain@linaro.org>,
	 kbuild-all@lists.01.org,
	 Linux Memory Management List <linux-mm@kvack.org>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>
Subject: Re: [linux-next:master 3307/5418] drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:3911:28: sparse: sparse: incorrect type in assignment (different base types)
Date: Wed, 08 Dec 2021 08:38:50 +0200	[thread overview]
Message-ID: <87y24vfvnp.fsf@codeaurora.org> (raw)
In-Reply-To: <202112080339.rKLd0aDI-lkp@intel.com> (kernel test robot's message of "Wed, 8 Dec 2021 03:24:25 +0800")

+ linux-wireless

kernel test robot <lkp@intel.com> writes:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   04fe99a8d936d46a310ca61b8b63dc270962bf01
> commit: 7a6cfe28ae3ef6a78774fd1e21e3b76c90937112 [3307/5418] brcmfmac:
> Configure keep-alive packet on suspend
> config: microblaze-randconfig-s031-20211207
> (https://download.01.org/0day-ci/archive/20211208/202112080339.rKLd0aDI-lkp@intel.com/config)
> compiler: microblaze-linux-gcc (GCC) 11.2.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=7a6cfe28ae3ef6a78774fd1e21e3b76c90937112
>         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 7a6cfe28ae3ef6a78774fd1e21e3b76c90937112
>         # save the config file to linux build tree
>         mkdir build_dir
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0
> make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir
> ARCH=microblaze SHELL=/bin/bash
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/
>
> 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/broadcom/brcm80211/brcmfmac/cfg80211.c:3911:28:
>>> sparse: sparse: incorrect type in assignment (different base types)
>>> @@ expected restricted __le32 [assigned] [usertype] period_msec @@
>>> got restricted __le16 [usertype] @@
>    drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:3911:28:
> sparse: expected restricted __le32 [assigned] [usertype] period_msec
>    drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:3911:28:
> sparse: got restricted __le16 [usertype]
>>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:3913:30:
>>> sparse: sparse: incorrect type in assignment (different base types)
>>> @@ expected unsigned char [assigned] [usertype] keep_alive_id @@
>>> got restricted __le16 [usertype] @@
>    drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:3913:30: sparse:     expected unsigned char [assigned] [usertype] keep_alive_id
>    drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:3913:30: sparse:     got restricted __le16 [usertype]

Loic, please send a fix for this.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


      reply	other threads:[~2021-12-08  6:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 19:24 [linux-next:master 3307/5418] drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:3911:28: sparse: sparse: incorrect type in assignment (different base types) kernel test robot
2021-12-08  6:38 ` Kalle Valo [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=87y24vfvnp.fsf@codeaurora.org \
    --to=kvalo@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=loic.poulain@linaro.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;
as well as URLs for NNTP newsgroup(s).