From: kbuild test robot <lkp@intel.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [gfs2:for-next.glock-refcount 4/6] fs/gfs2/lops.c:873:34: sparse: symbol 'gfs2_buf_lops' was not declared. Should it be static?
Date: Tue, 9 Apr 2019 00:42:39 +0800 [thread overview]
Message-ID: <201904090050.0WbeTSpF%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git for-next.glock-refcount
head: 047f2ad3806d5222110184ae156cb83e6f603eca
commit: 159238adb2acaf65a290da8f218ded616dc77e16 [4/6] gfs2: Remove unnecessary extern declarations
reproduce:
# apt-get install sparse
git checkout 159238adb2acaf65a290da8f218ded616dc77e16
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
sparse warnings: (new ones prefixed by >>)
include/linux/bvec.h:166:22: sparse: expression using sizeof(void)
include/linux/bvec.h:166:22: sparse: expression using sizeof(void)
>> fs/gfs2/lops.c:873:34: sparse: symbol 'gfs2_buf_lops' was not declared. Should it be static?
>> fs/gfs2/lops.c:882:34: sparse: symbol 'gfs2_revoke_lops' was not declared. Should it be static?
>> fs/gfs2/lops.c:891:34: sparse: symbol 'gfs2_databuf_lops' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2019-04-08 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 16:42 kbuild test robot [this message]
2019-04-08 16:42 ` [Cluster-devel] [RFC PATCH gfs2] gfs2: gfs2_buf_lops can be static 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=201904090050.0WbeTSpF%lkp@intel.com \
--to=lkp@intel.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).