From: Kalle Valo <kvalo@codeaurora.org>
To: kbuild test robot <lkp@intel.com>
Cc: Tzu-En Huang <tehuang@realtek.com>,
kbuild-all@lists.01.org, Yan-Hsuan Chuang <yhchuang@realtek.com>,
Chris Chiu <chiu@endlessm.com>,
linux-wireless@vger.kernel.org
Subject: Re: [wireless-drivers-next:master 89/97] drivers/net/wireless/realtek/rtw88/rtw8822b.c:1440:6: sparse: sparse: symbol 'rtw8822b_pwr_track' was not declared. Should it be static?
Date: Fri, 25 Oct 2019 07:21:23 +0300 [thread overview]
Message-ID: <875zkdjvzw.fsf@codeaurora.org> (raw)
In-Reply-To: <201910250727.FvcwI0W2%lkp@intel.com> (kbuild test robot's message of "Fri, 25 Oct 2019 07:55:48 +0800")
+ linux-wireless
Tony, can you send a followup patch to fix this as well?
Kalle
kbuild test robot <lkp@intel.com> writes:
> tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git
> master
> head: b298800dd8ee7250bf04b4dbd151e1a971b6df91
> commit: c97ee3e0bea29827f4b44276fc792bd32977edb0 [89/97] rtw88: add power tracking support
> reproduce:
> # apt-get install sparse
> # sparse version: v0.6.1-dirty
> git checkout c97ee3e0bea29827f4b44276fc792bd32977edb0
> make ARCH=x86_64 allmodconfig
> make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
>
> sparse warnings: (new ones prefixed by >>)
>
>>> drivers/net/wireless/realtek/rtw88/rtw8822b.c:1440:6: sparse:
> sparse: symbol 'rtw8822b_pwr_track' was not declared. Should it be
> static?
> --
>>> drivers/net/wireless/realtek/rtw88/rtw8822c.c:1008:6: sparse: sparse: symbol 'rtw8822c_pwrtrack_init' was not declared. Should it be static?
> drivers/net/wireless/realtek/rtw88/rtw8822c.c:2871:6: sparse: sparse: symbol 'rtw8822c_dpk_cal_coef1' was not declared. Should it be static?
> drivers/net/wireless/realtek/rtw88/rtw8822c.c:3112:6: sparse: sparse: symbol 'rtw8822c_dpk_track' was not declared. Should it be static?
>
> Please review and possibly fold the followup patch.
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: kbuild-all@lists.01.org
Subject: Re: [wireless-drivers-next:master 89/97] drivers/net/wireless/realtek/rtw88/rtw8822b.c:1440:6: sparse: sparse: symbol 'rtw8822b_pwr_track' was not declared. Should it be static?
Date: Fri, 25 Oct 2019 07:21:23 +0300 [thread overview]
Message-ID: <875zkdjvzw.fsf@codeaurora.org> (raw)
In-Reply-To: <201910250727.FvcwI0W2%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]
+ linux-wireless
Tony, can you send a followup patch to fix this as well?
Kalle
kbuild test robot <lkp@intel.com> writes:
> tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git
> master
> head: b298800dd8ee7250bf04b4dbd151e1a971b6df91
> commit: c97ee3e0bea29827f4b44276fc792bd32977edb0 [89/97] rtw88: add power tracking support
> reproduce:
> # apt-get install sparse
> # sparse version: v0.6.1-dirty
> git checkout c97ee3e0bea29827f4b44276fc792bd32977edb0
> make ARCH=x86_64 allmodconfig
> make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
>
> sparse warnings: (new ones prefixed by >>)
>
>>> drivers/net/wireless/realtek/rtw88/rtw8822b.c:1440:6: sparse:
> sparse: symbol 'rtw8822b_pwr_track' was not declared. Should it be
> static?
> --
>>> drivers/net/wireless/realtek/rtw88/rtw8822c.c:1008:6: sparse: sparse: symbol 'rtw8822c_pwrtrack_init' was not declared. Should it be static?
> drivers/net/wireless/realtek/rtw88/rtw8822c.c:2871:6: sparse: sparse: symbol 'rtw8822c_dpk_cal_coef1' was not declared. Should it be static?
> drivers/net/wireless/realtek/rtw88/rtw8822c.c:3112:6: sparse: sparse: symbol 'rtw8822c_dpk_track' was not declared. Should it be static?
>
> Please review and possibly fold the followup patch.
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
--
Kalle Valo
next prev parent reply other threads:[~2019-10-25 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 23:55 [wireless-drivers-next:master 89/97] drivers/net/wireless/realtek/rtw88/rtw8822b.c:1440:6: sparse: sparse: symbol 'rtw8822b_pwr_track' was not declared. Should it be static? kbuild test robot
2019-10-24 23:55 ` [RFC PATCH wireless-drivers-next] rtw88: rtw8822b_pwr_track() can be static kbuild test robot
2019-10-25 4:21 ` Kalle Valo [this message]
2019-10-25 4:21 ` [wireless-drivers-next:master 89/97] drivers/net/wireless/realtek/rtw88/rtw8822b.c:1440:6: sparse: sparse: symbol 'rtw8822b_pwr_track' was not declared. Should it be static? 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=875zkdjvzw.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=chiu@endlessm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=tehuang@realtek.com \
--cc=yhchuang@realtek.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.