From: Edward Shishkin <edward.shishkin@gmail.com>
To: Matthew Wilcox <willy@infradead.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
reiserfs-devel@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: Is it time to remove reiserfs?
Date: Mon, 21 Feb 2022 00:21:12 +0100 [thread overview]
Message-ID: <fbc744c9-e22f-138c-2da3-f76c3edfcc3d@gmail.com> (raw)
In-Reply-To: <YhIwUEpymVzmytdp@casper.infradead.org>
On 02/20/2022 01:13 PM, Matthew Wilcox wrote:
> Keeping reiserfs in the tree has certain costs. For example, I would
> very much like to remove the 'flags' argument to ->write_begin. We have
> the infrastructure in place to handle AOP_FLAG_NOFS differently, but
> AOP_FLAG_CONT_EXPAND is still around, used only by reiserfs.
Please, consider the patch (next email in the thread) which drops that
flag from reiserfs.
Thanks,
Edward.
next prev parent reply other threads:[~2022-02-20 23:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 12:13 Is it time to remove reiserfs? Matthew Wilcox
2022-02-20 23:21 ` Edward Shishkin [this message]
2022-02-20 23:22 ` [PATCH] reiserfs: get rid of AOP_FLAG_CONT_EXPAND flag Edward Shishkin
2022-02-22 10:27 ` Jan Kara
2022-02-22 13:38 ` Matthew Wilcox
2022-02-23 12:17 ` Jan Kara
2022-02-22 10:04 ` Is it time to remove reiserfs? Jan Kara
2022-02-22 22:16 ` Dave Chinner
2022-02-23 14:48 ` Byron Stanoszek
2022-02-23 15:28 ` Byron Stanoszek
2022-03-17 8:53 ` Thomas Dreibholz
2022-03-17 9:43 ` Jan Kara
2022-02-24 8:46 ` Jan Kara
2022-02-24 14:24 ` Byron Stanoszek
2022-02-24 21:06 ` Matthew Wilcox
2022-02-25 13:10 ` Byron Stanoszek
2022-02-25 13:23 ` Willy Tarreau
2022-02-25 22:56 ` Dave Chinner
2022-02-26 0:00 ` Theodore Ts'o
2022-04-02 10:57 ` Pavel Machek
2022-04-05 23:04 ` Dave Chinner
2022-04-02 10:54 ` Pavel Machek
2022-04-04 8:55 ` Jan Kara
2022-04-04 10:07 ` Pavel Machek
2022-04-04 10:18 ` Willy Tarreau
2022-04-04 10:58 ` Pavel Machek
2022-04-04 13:05 ` Jan Kara
2022-04-04 12:55 ` Jan Kara
2022-04-04 13:16 ` Willy Tarreau
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=fbc744c9-e22f-138c-2da3-f76c3edfcc3d@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=willy@infradead.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).