From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2 9/9] rtw88: 8723d: Add 8723DE to Kconfig and Makefile
Date: Tue, 12 May 2020 03:07:29 +0800 [thread overview]
Message-ID: <202005120230.86A2Fjow%lkp@intel.com> (raw)
In-Reply-To: <20200507042151.15634-10-yhchuang@realtek.com>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
Hi,
I love your patch! Perhaps something to improve:
[auto build test WARNING on wireless-drivers-next/master]
[cannot apply to wireless-drivers/master v5.7-rc5 next-20200511]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/yhchuang-realtek-com/rtw88-8723d-Add-RF-calibration-and-coex/20200507-134547
base: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git master
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-191-gc51a0382-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/net/wireless/realtek/rtw88/rtw8723d.c:1899:6: sparse: sparse: symbol 'rtw8723d_pwr_track' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: yhchuang@realtek.com, kvalo@codeaurora.org
Cc: kbuild-all@lists.01.org, linux-wireless@vger.kernel.org,
pkshih@realtek.com, bigeasy@linutronix.de
Subject: Re: [PATCH v2 9/9] rtw88: 8723d: Add 8723DE to Kconfig and Makefile
Date: Tue, 12 May 2020 03:07:29 +0800 [thread overview]
Message-ID: <202005120230.86A2Fjow%lkp@intel.com> (raw)
In-Reply-To: <20200507042151.15634-10-yhchuang@realtek.com>
Hi,
I love your patch! Perhaps something to improve:
[auto build test WARNING on wireless-drivers-next/master]
[cannot apply to wireless-drivers/master v5.7-rc5 next-20200511]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/yhchuang-realtek-com/rtw88-8723d-Add-RF-calibration-and-coex/20200507-134547
base: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git master
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-191-gc51a0382-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/net/wireless/realtek/rtw88/rtw8723d.c:1899:6: sparse: sparse: symbol 'rtw8723d_pwr_track' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2020-05-11 19:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 4:21 [PATCH v2 0/9] rtw88: 8723d: Add RF calibration and coex yhchuang
2020-05-07 4:21 ` [PATCH v2 1/9] rtw88: 8723d: Add LC calibration yhchuang
2020-05-12 8:49 ` Kalle Valo
2020-05-07 4:21 ` [PATCH v2 2/9] rtw88: 8723d: add IQ calibration yhchuang
2020-05-07 4:21 ` [PATCH v2 3/9] rtw88: 8723d: Add power tracking yhchuang
2020-05-07 4:21 ` [PATCH v2 4/9] rtw88: 8723d: Add shutdown callback to disable BT USB suspend yhchuang
2020-05-07 4:21 ` [PATCH v2 5/9] rtw88: 8723d: implement flush queue yhchuang
2020-05-07 4:21 ` [PATCH v2 6/9] rtw88: 8723d: set ltecoex register address in chip_info yhchuang
2020-05-07 4:21 ` [PATCH v2 7/9] rtw88: 8723d: Add coex support yhchuang
2020-05-07 4:21 ` [PATCH v2 8/9] rtw88: fill zeros to words 0x06 and 0x07 of security cam entry yhchuang
2020-05-07 4:21 ` [PATCH v2 9/9] rtw88: 8723d: Add 8723DE to Kconfig and Makefile yhchuang
2020-05-11 19:07 ` kbuild test robot [this message]
2020-05-11 19:07 ` kbuild test robot
2020-05-11 19:07 ` [RFC PATCH] rtw88: 8723d: rtw8723d_pwr_track() can be static kbuild test robot
2020-05-11 19:07 ` kbuild test robot
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=202005120230.86A2Fjow%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.