From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [freescale-fslc:pr/225 247/432] net/dsa/dsa2.c:127:17: sparse: sparse: symbol 'dsa_link_touch' was not declared. Should it be
Date: Fri, 22 Jan 2021 13:50:17 +0800 [thread overview]
Message-ID: <202101221355.yoGRJO0f-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
tree: https://github.com/Freescale/linux-fslc pr/225
head: ab134276e5fa0f228a300c61bed6c8b61a17393b
commit: 27f0edf01bae213fe59f0205154ff871ead4b0ca [247/432] net: dsa: list DSA links in the fabric
config: i386-randconfig-s002-20210122 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-208-g46a52ca4-dirty
# https://github.com/Freescale/linux-fslc/commit/27f0edf01bae213fe59f0205154ff871ead4b0ca
git remote add freescale-fslc https://github.com/Freescale/linux-fslc
git fetch --no-tags freescale-fslc pr/225
git checkout 27f0edf01bae213fe59f0205154ff871ead4b0ca
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
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 >>)"
>> net/dsa/dsa2.c:127:17: sparse: sparse: symbol 'dsa_link_touch' 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: 33458 bytes --]
next reply other threads:[~2021-01-22 5:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 5:50 kernel test robot [this message]
2021-01-22 5:50 ` [RFC PATCH freescale-fslc] net: dsa: dsa_link_touch() can be static 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=202101221355.yoGRJO0f-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.