linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Chi-Hsien Lin <chi-hsien.lin@cypress.com>
Cc: kernel test robot <lkp@intel.com>,
	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:55:20 +0300	[thread overview]
Message-ID: <875zbjf8vb.fsf@codeaurora.org> (raw)
In-Reply-To: <76e75ef2-850b-2860-f28b-ba773ee50117@cypress.com> (Chi-Hsien Lin's message of "Mon, 22 Jun 2020 22:48:18 +0800")

Chi-Hsien Lin <chi-hsien.lin@cypress.com> writes:

> On 06/22/2020 10:09, Kalle Valo wrote:
>> + 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.
> Kalle,
>
> The fix is this one
> https://patchwork.kernel.org/patch/11598109/

Great, thanks.

> Do I need to submit a V2 with "Reported-by: kernel test robot
> <lkp@intel.com>" tag?

No need to send v2. But you can reply to that patch (so that patchwork
sees it) and ask me to add the tag during commit.

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

      reply	other threads:[~2020-06-22 14:55 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 ` drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c:1710:40: sparse: sparse: incorrect type in initializer (different base types) Kalle Valo
2020-06-22 14:48   ` Chi-Hsien Lin
2020-06-22 14:55     ` 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=875zbjf8vb.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=chi-hsien.lin@cypress.com \
    --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).