From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH djwong-xfs] xfs: xbtree_fakeroot_dup_cursor can be static
Date: Tue, 08 Oct 2019 12:59:58 +0800 [thread overview]
Message-ID: <20191008045958.uovw3mabslnhdukm@332d0cec05f4> (raw)
In-Reply-To: <201910081219.GBOVk3dt%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
Fixes: 51e7c56bff7e ("xfs: introduce fake roots for ag-rooted btrees")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
xfs_btree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xfs/libxfs/xfs_btree.c b/fs/xfs/libxfs/xfs_btree.c
index 092004a6ea461f..35ca2264ccd11b 100644
--- a/fs/xfs/libxfs/xfs_btree.c
+++ b/fs/xfs/libxfs/xfs_btree.c
@@ -4934,7 +4934,7 @@ xfs_btree_has_more_records(
}
/* We don't allow staging cursors to be duplicated. */
-struct xfs_btree_cur *
+static struct xfs_btree_cur *
xbtree_fakeroot_dup_cursor(
struct xfs_btree_cur *cur)
{
prev parent 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 [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? kbuild test robot
2019-10-08 4:59 ` kbuild test robot [this message]
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=20191008045958.uovw3mabslnhdukm@332d0cec05f4 \
--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.