From: Kalle Valo <kvalo@kernel.org>
To: Li Qiong <liqiong@nfschina.com>
Cc: Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Yu Zhe <yuzhe@nfschina.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wifi: cfg80211: add error code in brcmf_notify_sched_scan_results()
Date: Mon, 29 Aug 2022 10:59:35 +0300 [thread overview]
Message-ID: <87edwzjx94.fsf@kernel.org> (raw)
In-Reply-To: <20220829065831.14023-1-liqiong@nfschina.com> (Li Qiong's message of "Mon, 29 Aug 2022 14:58:31 +0800")
+ linux-wireless
Li Qiong <liqiong@nfschina.com> writes:
> The err code is 0 at the first two "out_err" paths, add error code
> '-EINVAL' for these error paths.
>
> Signed-off-by: Li Qiong <liqiong@nfschina.com>
> ---
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 2 ++
> 1 file changed, 2 insertions(+)
You need to CC linux-wireless, otherwise patchwork won't see it. Also
the title should be:
wifi: brcmfmac: add error code in brcmf_notify_sched_scan_results()
Please resubmit as v2.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-08-29 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 6:58 [PATCH] wifi: cfg80211: add error code in brcmf_notify_sched_scan_results() Li Qiong
2022-08-29 7:59 ` Kalle Valo [this message]
2022-08-29 8:51 ` Arend Van Spriel
2022-08-29 11:31 ` liqiong
2022-08-29 11:12 ` [PATCH v2] wifi: brcmfmac: " Li Qiong
2022-09-07 7:29 ` 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=87edwzjx94.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=aspriel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=liqiong@nfschina.com \
--cc=netdev@vger.kernel.org \
--cc=yuzhe@nfschina.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 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.