From: Kalle Valo <kvalo@codeaurora.org>
To: kernel test robot <lkp@intel.com>
Cc: Joseph Chuang <joseph.chuang@cypress.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c:1710:40: sparse: sparse: incorrect type in initializer (different base types)
Date: Mon, 22 Jun 2020 17:09:24 +0300 [thread overview]
Message-ID: <87a70vgpkb.fsf@codeaurora.org> (raw)
In-Reply-To: <202006190422.VymyEbuu%lkp@intel.com> (kernel test robot's message of "Fri, 19 Jun 2020 04:37:24 +0800")
+ linux-wireless
kernel test robot <lkp@intel.com> writes:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 5e857ce6eae7ca21b2055cca4885545e29228fe2
> commit: 9c29da3f4e7ef9810bdfaf3d8aa5e6d2e33136f8 brcmfmac: Fix P2P
> Group Formation failure via Go-neg method
> date: 6 weeks ago
> config: riscv-randconfig-s032-20200618 (attached as .config)
> compiler: riscv64-linux-gcc (GCC) 9.3.0
> reproduce:
> # apt-get install sparse
> # sparse version: v0.6.2-rc1-10-gc17b1b06-dirty
> git checkout 9c29da3f4e7ef9810bdfaf3d8aa5e6d2e33136f8
> # save the attached .config to linux build tree
> make W=1 C=1 ARCH=riscv CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
>
> 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/p2p.c:1710:40:
>>> sparse: sparse: incorrect type in initializer (different base
>>> types) @@ expected signed int [usertype] requested_dwell @@ got
>>> restricted __le32 [usertype] dwell_time @@
>>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c:1710:40:
>>> sparse: expected signed int [usertype] requested_dwell
>>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c:1710:40:
>>> sparse: got restricted __le32 [usertype] dwell_time
Joseph, please send a followup patch to fix these.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next parent reply other threads:[~2020-06-22 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202006190422.VymyEbuu%lkp@intel.com>
2020-06-22 14:09 ` Kalle Valo [this message]
2020-06-22 14:48 ` drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c:1710:40: sparse: sparse: incorrect type in initializer (different base types) Chi-Hsien Lin
2020-06-22 14:55 ` 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=87a70vgpkb.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=joseph.chuang@cypress.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).