From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 1/2] btrfs: remove deprecated mount option alloc_start
Date: Wed, 1 Jul 2020 17:16:15 +0200 [thread overview]
Message-ID: <a0da2bf1c12108891964c437d3c6db5b6eed9926.1593616511.git.dsterba@suse.com> (raw)
In-Reply-To: <cover.1593616511.git.dsterba@suse.com>
The mount option alloc_start has no effect since 0d0c71b31720 ("btrfs:
obsolete and remove mount option alloc_start") which has details why
it's been deprecated. We can remove it.
Signed-off-by: David Sterba <dsterba@suse.com>
---
fs/btrfs/super.c | 6 ------
1 file changed, 6 deletions(-)
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index 3c9ebd4f2b61..7e204b42076d 100644
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -348,7 +348,6 @@ enum {
Opt_rescue_skipbg,
/* Deprecated options */
- Opt_alloc_start,
Opt_recovery,
Opt_subvolrootid,
@@ -421,7 +420,6 @@ static const match_table_t tokens = {
{Opt_usebackuproot, "usebackuproot"},
/* Deprecated options */
- {Opt_alloc_start, "alloc_start=%s"},
{Opt_recovery, "recovery"},
{Opt_subvolrootid, "subvolrootid=%d"},
@@ -726,10 +724,6 @@ int btrfs_parse_options(struct btrfs_fs_info *info, char *options,
goto out;
}
break;
- case Opt_alloc_start:
- btrfs_info(info,
- "option alloc_start is obsolete, ignored");
- break;
case Opt_acl:
#ifdef CONFIG_BTRFS_FS_POSIX_ACL
info->sb->s_flags |= SB_POSIXACL;
--
2.25.0
next prev parent reply other threads:[~2020-07-01 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 15:16 [PATCH 0/2] Removal of deprecated mount options David Sterba
2020-07-01 15:16 ` David Sterba [this message]
2020-07-01 15:16 ` [PATCH 2/2] btrfs: remove deprecated mount option subvolrootid 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=a0da2bf1c12108891964c437d3c6db5b6eed9926.1593616511.git.dsterba@suse.com \
--to=dsterba@suse.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.