From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-next:master 8852/10007] drivers/net/mhi/net.c:385:23: sparse: sparse: symbol 'mhi_wwan_ops' was not declared. Should it be static?
Date: Wed, 16 Jun 2021 02:14:42 +0800 [thread overview]
Message-ID: <202106160258.T7fXJrOX-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 19ae1f2bd9c091059f80646604ccef8a1e614f57
commit: 13adac032982c61bb590669e8e87e51558917ca1 [8852/10007] net: mhi_net: Register wwan_ops for link creation
config: x86_64-randconfig-s021-20210615 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=13adac032982c61bb590669e8e87e51558917ca1
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 13adac032982c61bb590669e8e87e51558917ca1
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/net/mhi/net.c:385:23: sparse: sparse: symbol 'mhi_wwan_ops' 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
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 37625 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Loic Poulain <loic.poulain@linaro.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 8852/10007] drivers/net/mhi/net.c:385:23: sparse: sparse: symbol 'mhi_wwan_ops' was not declared. Should it be static?
Date: Wed, 16 Jun 2021 02:14:42 +0800 [thread overview]
Message-ID: <202106160258.T7fXJrOX-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 19ae1f2bd9c091059f80646604ccef8a1e614f57
commit: 13adac032982c61bb590669e8e87e51558917ca1 [8852/10007] net: mhi_net: Register wwan_ops for link creation
config: x86_64-randconfig-s021-20210615 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=13adac032982c61bb590669e8e87e51558917ca1
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 13adac032982c61bb590669e8e87e51558917ca1
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/net/mhi/net.c:385:23: sparse: sparse: symbol 'mhi_wwan_ops' 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
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37625 bytes --]
next reply other threads:[~2021-06-15 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 18:14 kernel test robot [this message]
2021-06-15 18:14 ` [linux-next:master 8852/10007] drivers/net/mhi/net.c:385:23: sparse: sparse: symbol 'mhi_wwan_ops' was not declared. Should it be static? kernel test robot
2021-06-15 18:14 ` [RFC PATCH linux-next] net: mhi_net: mhi_wwan_ops can be static kernel test robot
2021-06-15 18:14 ` kernel 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=202106160258.T7fXJrOX-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.