From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [djwong-xfs:getfsmap-cleanups-5.10 105/105] fs/xfs/xfs_fsmap.c:30:1: sparse: sparse: symbol 'xfs_fsmap_from_internal' was not declared. Should it be
Date: Fri, 02 Oct 2020 17:12:47 +0800 [thread overview]
Message-ID: <202010021713.AA889qRH-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git getfsmap-cleanups-5.10
head: 9247e7816067141457e5eb9b84c3070a7905d111
commit: 9247e7816067141457e5eb9b84c3070a7905d111 [105/105] xfs: streamline xfs_getfsmap performance
config: x86_64-randconfig-s021-20201002 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-201-g24bdaac6-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/commit/?id=9247e7816067141457e5eb9b84c3070a7905d111
git remote add djwong-xfs https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git
git fetch --no-tags djwong-xfs getfsmap-cleanups-5.10
git checkout 9247e7816067141457e5eb9b84c3070a7905d111
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
echo
echo "sparse warnings: (new ones prefixed by >>)"
echo
>> fs/xfs/xfs_fsmap.c:30:1: sparse: sparse: symbol 'xfs_fsmap_from_internal' 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: 39380 bytes --]
next reply other threads:[~2020-10-02 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 9:12 kernel test robot [this message]
2020-10-02 9:12 ` [RFC PATCH djwong-xfs] xfs: xfs_fsmap_from_internal 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=202010021713.AA889qRH-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.