All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [djwong-xfs:rough-fixes 8/133] fs/xfs/libxfs/xfs_btree.c:4937:22: sparse: sparse: symbol 'xbtree_fakeroot_dup_cursor' was not declared. Should it be static?
Date: Tue, 08 Oct 2019 12:59:57 +0800	[thread overview]
Message-ID: <201910081219.GBOVk3dt%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git rough-fixes
head:   73421a54a60e2b4bcac0d82321b24e73e2a8f0ab
commit: 51e7c56bff7e0c6576e4532432c2c83734b0c8b1 [8/133] xfs: introduce fake roots for ag-rooted btrees
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-rc1-42-g38eda53-dirty
        git checkout 51e7c56bff7e0c6576e4532432c2c83734b0c8b1
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

>> fs/xfs/libxfs/xfs_btree.c:4937:22: sparse: sparse: symbol 'xbtree_fakeroot_dup_cursor' 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

             reply	other threads:[~2019-10-08  4:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08  4:59 kbuild test robot [this message]
2019-10-08  4:59 ` [RFC PATCH djwong-xfs] xfs: xbtree_fakeroot_dup_cursor 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=201910081219.GBOVk3dt%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.