From: kernel test robot <lkp@intel.com>
To: Loic Poulain <loic.poulain@linaro.org>,
kuba@kernel.org, davem@davemloft.net, gregkh@linuxfoundation.org
Cc: kbuild-all@lists.01.org, linux-arm-msm@vger.kernel.org,
aleksander@aleksander.es, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, bjorn.andersson@linaro.org,
manivannan.sadhasivam@linaro.org, hemantk@codeaurora.org
Subject: Re: [PATCH net-next v4 1/2] net: Add a WWAN subsystem
Date: Fri, 12 Mar 2021 02:52:27 +0800 [thread overview]
Message-ID: <202103120220.FEMZs8mU-lkp@intel.com> (raw)
In-Reply-To: <1615480746-28518-1-git-send-email-loic.poulain@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1986 bytes --]
Hi Loic,
I love your patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Loic-Poulain/net-Add-a-WWAN-subsystem/20210312-003256
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 34bb975126419e86bc3b95e200dc41de6c6ca69c
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/259571a34d6f035f99a8343c5fcd12b6dfc92c40
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Loic-Poulain/net-Add-a-WWAN-subsystem/20210312-003256
git checkout 259571a34d6f035f99a8343c5fcd12b6dfc92c40
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=m68k
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/net/wwan/wwan_core.c:22:21: warning: no previous prototype for '__wwan_find_by_parent' [-Wmissing-prototypes]
22 | struct wwan_device *__wwan_find_by_parent(struct device *parent)
| ^~~~~~~~~~~~~~~~~~~~~
vim +/__wwan_find_by_parent +22 drivers/net/wwan/wwan_core.c
21
> 22 struct wwan_device *__wwan_find_by_parent(struct device *parent)
23 {
24 struct wwan_device *wwandev;
25
26 if (!parent)
27 return NULL;
28
29 list_for_each_entry(wwandev, &wwan_list, list) {
30 if (wwandev->dev.parent == parent)
31 return wwandev;
32 }
33
34 return NULL;
35 }
36
---
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: 59865 bytes --]
prev parent reply other threads:[~2021-03-11 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 16:39 [PATCH net-next v4 1/2] net: Add a WWAN subsystem Loic Poulain
2021-03-11 16:39 ` [PATCH net-next v4 2/2] net: Add Qcom WWAN control driver Loic Poulain
2021-03-11 18:58 ` Randy Dunlap
2021-03-11 16:48 ` [PATCH net-next v4 1/2] net: Add a WWAN subsystem Greg KH
2021-03-11 17:14 ` Loic Poulain
2021-03-11 16:48 ` Greg KH
2021-03-11 18:52 ` kernel 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=202103120220.FEMZs8mU-lkp@intel.com \
--to=lkp@intel.com \
--cc=aleksander@aleksander.es \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hemantk@codeaurora.org \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox