From: Kalle Valo <kvalo@codeaurora.org>
To: Chris Chiu <chiu@endlessm.com>
Cc: linux-wireless@vger.kernel.org
Subject: rtl8xxxu: recent sparse warnings
Date: Wed, 23 Oct 2019 13:07:40 +0300 [thread overview]
Message-ID: <87imofu64z.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5db0120f.6XzlR4e8kc/qgxwe%lkp@intel.com> (kbuild test robot's message of "Wed, 23 Oct 2019 16:40:47 +0800")
kbuild test robot <lkp@intel.com> writes:
> tree/branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git
> master
> branch HEAD: 0eeb91ade90ce06d2fa1e2fcb55e3316b64c203c rtl8xxxu: fix
> RTL8723BU connection failure issue after warm reboot
>
> Regressions in current branch:
>
> drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c:5197:6: sparse:
> sparse: symbol 'rtl8723bu_set_coex_with_type' was not declared. Should
> it be static?
> drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c:5248:6: sparse:
> sparse: symbol 'rtl8723bu_update_bt_link_info' was not declared.
> Should it be static?
> drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c:5314:6: sparse:
> sparse: symbol 'rtl8723bu_handle_bt_inquiry' was not declared. Should
> it be static?
> drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c:5339:6: sparse:
> sparse: symbol 'rtl8723bu_handle_bt_info' was not declared. Should it
> be static?
Chris, I believe these sparse warnings come from your commit:
e542e66b7c2e rtl8xxxu: add bluetooth co-existence support for single antenna
Can you send a follow up patch to fix these, please?
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
parent reply other threads:[~2019-10-23 10:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5db0120f.6XzlR4e8kc/qgxwe%lkp@intel.com>]
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=87imofu64z.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=chiu@endlessm.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.