From: Kalle Valo <kvalo@kernel.org>
To: Ian Lin <ian.lin@infineon.com>
Cc: <linux-wireless@vger.kernel.org>,
<brcm80211-dev-list@broadcom.com>,
<brcm80211-dev-list@cypress.com>, <franky.lin@broadcom.com>,
<hante.meuleman@broadcom.com>, <Double.Lo@infineon.com>
Subject: Re: [PATCH v3 0/5] Fix connect/p2p issue series
Date: Wed, 28 Sep 2022 09:33:22 +0300 [thread overview]
Message-ID: <878rm4rost.fsf@kernel.org> (raw)
In-Reply-To: <20220927034138.20463-1-ian.lin@infineon.com> (Ian Lin's message of "Mon, 26 Sep 2022 22:41:33 -0500")
Ian Lin <ian.lin@infineon.com> writes:
> Fix several connect and p2p issues.
>
> Note: there will be known build warning with commit
> "fix P2P device discovery failure"
> - warning: parameter ‘vif’ set but not used [-Wunused-but-set-parameter]
> However the purpose is to overwrite the pointer(vif) in function parameter,
> and the pointer will be used ouside the function.
We have a rule that there can be no build warnings so this needs to
solved somehow.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2022-09-28 6:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 3:41 [PATCH v3 0/5] Fix connect/p2p issue series Ian Lin
2022-09-27 3:41 ` [PATCH v3 1/5] brcmfmac: correctly remove all p2p vif Ian Lin
2022-09-27 3:41 ` [PATCH v3 2/5] brcmfmac: Fix for when connect request is not success Ian Lin
2022-09-27 3:41 ` [PATCH v3 3/5] brcmfmac: Avoiding Connection delay Ian Lin
2022-09-27 3:41 ` [PATCH v3 4/5] brcmfmac: Update SSID of hidden AP while informing its bss to cfg80211 layer Ian Lin
2022-09-28 6:38 ` Kalle Valo
2022-09-28 10:07 ` Lin Ian (CSSITB CSS ICW SW WFS / EE)
2022-10-04 11:01 ` Lin Ian (CSSITB CSS ICW SW WFS / EE)
2022-10-05 7:58 ` Kalle Valo
2022-10-05 10:22 ` Arend Van Spriel
2022-10-06 8:34 ` Lin Ian (CSSITB CSS ICW SW WFS / EE)
2022-10-10 9:23 ` Arend Van Spriel
2022-10-10 9:41 ` Johannes Berg
2022-10-10 11:18 ` Arend Van Spriel
2022-09-27 3:41 ` [PATCH v3 5/5] brcmfmac: fix P2P device discovery failure Ian Lin
2022-09-28 6:33 ` 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=878rm4rost.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Double.Lo@infineon.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=ian.lin@infineon.com \
--cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.