linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Colin Ian King <colin.king@canonical.com>,
	David Sterba <dsterba@suse.com>
Subject: [PATCH 4/4] btrfs: remove duplicate const specifier
Date: Tue, 19 Jan 2016 11:43:57 +0100	[thread overview]
Message-ID: <fb75d857a31d600cc0c37b8c7d914014f7fa3f9a.1453199864.git.dsterba@suse.com> (raw)
In-Reply-To: <cover.1453199864.git.dsterba@suse.com>

From: Colin Ian King <colin.king@canonical.com>

duplicate const is redundant so remove it

Signed-off-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: David Sterba <dsterba@suse.com>
---
 fs/btrfs/volumes.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index 9cb78e31fc76..78f76958b855 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -108,7 +108,7 @@ const struct btrfs_raid_attr btrfs_raid_array[BTRFS_NR_RAID_TYPES] = {
 	},
 };
 
-const u64 const btrfs_raid_group[BTRFS_NR_RAID_TYPES] = {
+const u64 btrfs_raid_group[BTRFS_NR_RAID_TYPES] = {
 	[BTRFS_RAID_RAID10] = BTRFS_BLOCK_GROUP_RAID10,
 	[BTRFS_RAID_RAID1]  = BTRFS_BLOCK_GROUP_RAID1,
 	[BTRFS_RAID_DUP]    = BTRFS_BLOCK_GROUP_DUP,
-- 
2.6.3


      parent reply	other threads:[~2016-01-19 10:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 10:43 [PULL][PATCH 0/4] Btrfs: cleanups for 4.5, part 2 David Sterba
2016-01-19 10:43 ` [PATCH 1/4] btrfs: cleanup, stop casting for extent_map->lookup everywhere David Sterba
2016-01-19 10:43 ` [PATCH 2/4] btrfs: fix iterator with update error in backref.c David Sterba
2016-01-19 10:43 ` [PATCH 3/4] Btrfs: clean up an error code in btrfs_init_space_info() David Sterba
2016-01-19 10:43 ` David Sterba [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=fb75d857a31d600cc0c37b8c7d914014f7fa3f9a.1453199864.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=colin.king@canonical.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 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).