All of lore.kernel.org
 help / color / mirror / Atom feed
From: Byongho Lee <bhlee.kernel@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 3/6] btrfs-progs: make private symbols to static
Date: Mon,  4 Jan 2016 10:01:31 +0900	[thread overview]
Message-ID: <1451869294-4291-4-git-send-email-bhlee.kernel@gmail.com> (raw)
In-Reply-To: <1451869294-4291-1-git-send-email-bhlee.kernel@gmail.com>

Signed-off-by: Byongho Lee <bhlee.kernel@gmail.com>
---
 btrfs-show-super.c | 4 ++--
 qgroup-verify.c    | 8 ++++----
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/btrfs-show-super.c b/btrfs-show-super.c
index c0ffeacb928c..f11701539d1a 100644
--- a/btrfs-show-super.c
+++ b/btrfs-show-super.c
@@ -334,7 +334,7 @@ struct readable_flag_entry {
 #define DEF_INCOMPAT_FLAG_ENTRY(bit_name)		\
 	{BTRFS_FEATURE_INCOMPAT_##bit_name, #bit_name}
 
-struct readable_flag_entry incompat_flags_array[] = {
+static struct readable_flag_entry incompat_flags_array[] = {
 	DEF_INCOMPAT_FLAG_ENTRY(MIXED_BACKREF),
 	DEF_INCOMPAT_FLAG_ENTRY(DEFAULT_SUBVOL),
 	DEF_INCOMPAT_FLAG_ENTRY(MIXED_GROUPS),
@@ -354,7 +354,7 @@ static const int incompat_flags_num = sizeof(incompat_flags_array) /
 #define DEF_SUPER_FLAG_ENTRY(bit_name)			\
 	{BTRFS_SUPER_FLAG_##bit_name, #bit_name}
 
-struct readable_flag_entry super_flags_array[] = {
+static struct readable_flag_entry super_flags_array[] = {
 	DEF_HEADER_FLAG_ENTRY(WRITTEN),
 	DEF_HEADER_FLAG_ENTRY(RELOC),
 	DEF_SUPER_FLAG_ENTRY(CHANGING_FSID),
diff --git a/qgroup-verify.c b/qgroup-verify.c
index f7a94bfb0d32..0ee52ff5c857 100644
--- a/qgroup-verify.c
+++ b/qgroup-verify.c
@@ -49,12 +49,12 @@ struct qgroup_count {
 	struct rb_node			rb_node;
 };
 
-struct counts_tree {
+static struct counts_tree {
 	struct rb_root		root;
 	unsigned int		num_groups;
 } counts = { .root = RB_ROOT };
 
-struct rb_root by_bytenr = RB_ROOT;
+static struct rb_root by_bytenr = RB_ROOT;
 
 /*
  * List of interior tree blocks. We walk this list after loading the
@@ -68,8 +68,8 @@ struct rb_root by_bytenr = RB_ROOT;
  * exist further down the tree, the fact that our interior node has a
  * ref means we need to account anything below it to all its roots.
  */
-struct ulist *tree_blocks = NULL;	/* unode->val = bytenr, ->aux
-					 * = tree_block pointer */
+static struct ulist *tree_blocks = NULL;	/* unode->val = bytenr, ->aux
+						 * = tree_block pointer */
 struct tree_block {
 	int			level;
 	u64			num_bytes;
-- 
2.6.4


  parent reply	other threads:[~2016-01-04  1:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04  1:01 [PATCH v2 0/6] btrfs-progs: fix endian bugs and clean-ups Byongho Lee
2016-01-04  1:01 ` [PATCH v2 1/6] btrfs-progs: get sparse checking working Byongho Lee
2016-01-04  1:01 ` [PATCH v2 2/6] btrfs-progs: use NULL instead of 0 Byongho Lee
2016-01-04  1:01 ` Byongho Lee [this message]
2016-01-04  1:01 ` [PATCH v2 4/6] btrfs-progs: fix endian bugs in chunk rebuilding Byongho Lee
2016-01-04  1:01 ` [PATCH v2 5/6] btrfs-progs: fix endian bug in update_super() Byongho Lee
2016-01-04  1:01 ` [PATCH v2 6/6] btrfs-progs: fix using on-disk structure to store in memory data Byongho Lee
2016-01-04  9:59 ` [PATCH v2 0/6] btrfs-progs: fix endian bugs and clean-ups 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=1451869294-4291-4-git-send-email-bhlee.kernel@gmail.com \
    --to=bhlee.kernel@gmail.com \
    --cc=linux-btrfs@vger.kernel.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.