From: kbuild test robot <lkp@intel.com>
To: yhchuang@realtek.com
Cc: kbuild-all@lists.01.org, kvalo@codeaurora.org,
linux-wireless@vger.kernel.org, briannorris@chromium.org,
tehuang@realtek.com
Subject: Re: [PATCH v4 2/2] rtw88: add adaptivity support for EU/JP regulatory
Date: Thu, 12 Mar 2020 07:28:45 +0800 [thread overview]
Message-ID: <202003120721.jj0a0BdT%lkp@intel.com> (raw)
In-Reply-To: <20200311094524.18884-3-yhchuang@realtek.com>
[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]
Hi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on wireless-drivers-next/master]
[also build test WARNING on next-20200311]
[cannot apply to wireless-drivers/master v5.6-rc5]
[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-update-regulatory-settings/20200312-042059
base: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git master
config: parisc-allyesconfig (attached as .config)
compiler: hppa-linux-gcc (GCC) 9.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=9.2.0 make.cross ARCH=parisc
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/net//wireless/realtek/rtw88/debug.c: In function 'rtw_debugfs_set_edcca_enable':
>> drivers/net//wireless/realtek/rtw88/debug.c:707:2: warning: ignoring return value of 'kstrtobool', declared with attribute warn_unused_result [-Wunused-result]
707 | kstrtobool(tmp, &rtw_edcca_enabled);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/kstrtobool +707 drivers/net//wireless/realtek/rtw88/debug.c
696
697 static ssize_t rtw_debugfs_set_edcca_enable(struct file *filp,
698 const char __user *buffer,
699 size_t count, loff_t *loff)
700 {
701 struct rtw_debugfs_priv *debugfs_priv = filp->private_data;
702 struct rtw_dev *rtwdev = debugfs_priv->rtwdev;
703 char tmp[32 + 1];
704
705 rtw_debugfs_copy_from_user(tmp, sizeof(tmp), buffer, count, 1);
706
> 707 kstrtobool(tmp, &rtw_edcca_enabled);
708 rtw_phy_adaptivity_set_mode(rtwdev);
709
710 return count;
711 }
712
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 60340 bytes --]
prev parent reply other threads:[~2020-03-11 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 9:45 [PATCH v4 0/2] rtw88: update regulatory settings yhchuang
2020-03-11 9:45 ` [PATCH v4 1/2] rtw88: add regulatory process strategy for different chipset yhchuang
2020-03-11 9:45 ` [PATCH v4 2/2] rtw88: add adaptivity support for EU/JP regulatory yhchuang
2020-03-11 23:28 ` kbuild test robot [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=202003120721.jj0a0BdT%lkp@intel.com \
--to=lkp@intel.com \
--cc=briannorris@chromium.org \
--cc=kbuild-all@lists.01.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).