From: kbuild test robot <lkp@intel.com>
To: Mark Fasheh <mfasheh@suse.de>
Cc: kbuild-all@01.org, linux-btrfs@vger.kernel.org, jbacik@fb.com,
clm@fb.com, david@fromorbit.com
Subject: [RFC PATCH] btrfs: drop_status_lock can be static
Date: Fri, 2 Oct 2015 06:26:24 +0800 [thread overview]
Message-ID: <20151001222624.GA2456@lkp-nex05> (raw)
In-Reply-To: <20151001213047.GB1044@wotan.suse.de>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
extent-tree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index 75f499e..0e9a9f1 100644
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -8465,7 +8465,7 @@ static noinline int walk_up_tree(struct btrfs_trans_handle *trans,
return 1;
}
-DEFINE_SPINLOCK(drop_status_lock);
+static DEFINE_SPINLOCK(drop_status_lock);
void btrfs_add_drop_status(struct btrfs_root *root)
{
struct btrfs_fs_info *fs_info = root->fs_info;
next prev parent reply other threads:[~2015-10-01 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201510020624.ABe5GlB7%fengguang.wu@intel.com>
2015-10-01 21:30 ` [RFC][PATCH] btrfs: add ioctl to monitor subvolume dropping Mark Fasheh
2015-10-01 22:26 ` kbuild test robot [this message]
2015-10-06 8:25 ` David Sterba
2015-10-06 17:09 ` Mark Fasheh
2015-10-06 19:42 ` Mark Fasheh
2015-10-07 9:46 ` David Sterba
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=20151001222624.GA2456@lkp-nex05 \
--to=lkp@intel.com \
--cc=clm@fb.com \
--cc=david@fromorbit.com \
--cc=jbacik@fb.com \
--cc=kbuild-all@01.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfasheh@suse.de \
/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).