From: Steven Davies <btrfs-list@steev.me.uk>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: start deprecation of mount option inode_cache
Date: Wed, 24 Jun 2020 08:37:13 +0100 [thread overview]
Message-ID: <076d047d33676d78e882feb74a2f0c4f@steev.me.uk> (raw)
In-Reply-To: <20200623185032.14983-1-dsterba@suse.com>
On 2020-06-23 19:50, David Sterba wrote:
> @@ -827,6 +827,8 @@ int btrfs_parse_options(struct btrfs_fs_info
> *info, char *options,
> }
> break;
> case Opt_inode_cache:
> + btrfs_warn(info,
> + "the 'inode_cache' option is deprecated and will be stop working in
> 5.11");
"will stop working", but perhaps "will have no effect from" might be
more explicit.
--
Steven Davies
next prev parent reply other threads:[~2020-06-24 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 18:50 [PATCH] btrfs: start deprecation of mount option inode_cache David Sterba
2020-06-23 23:27 ` Qu Wenruo
2020-06-24 11:00 ` David Sterba
2020-06-24 11:06 ` Qu Wenruo
2020-06-24 7:37 ` Steven Davies [this message]
2020-06-24 9:55 ` David Sterba
2020-07-07 17:14 ` 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=076d047d33676d78e882feb74a2f0c4f@steev.me.uk \
--to=btrfs-list@steev.me.uk \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox