From: Matthew Wilcox <willy@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Edward Shishkin <edward.shishkin@gmail.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
reiserfs-devel@vger.kernel.org
Subject: Re: [PATCH] reiserfs: get rid of AOP_FLAG_CONT_EXPAND flag
Date: Tue, 22 Feb 2022 13:38:19 +0000 [thread overview]
Message-ID: <YhTnSwmHVRe5AzJQ@casper.infradead.org> (raw)
In-Reply-To: <20220222102727.2sqf4wfdtjaxrqat@quack3.lan>
On Tue, Feb 22, 2022 at 11:27:27AM +0100, Jan Kara wrote:
> On Mon 21-02-22 00:22:19, Edward Shishkin wrote:
> > Signed-off-by: Edward Shishkin <edward.shishkin@gmail.com>
> > ---
> > fs/reiserfs/inode.c | 16 +++++-----------
> > 1 file changed, 5 insertions(+), 11 deletions(-)
>
> Thanks! I have queued this patch into my tree.
I added the following commit message to it for my tree:
Author: Edward Shishkin <edward.shishkin@gmail.com>
Date: Mon Feb 21 00:22:19 2022 +0100
reiserfs: Stop using AOP_FLAG_CONT_EXPAND flag
We can simplify write_begin() and write_end() by handling the
cont_expand case in reiserfs_setattr().
Signed-off-by: Edward Shishkin <edward.shishkin@gmail.com>
Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
I don't object if it goes via your tree; I doubt I'll get the AOP_FLAG
removal finished in time for the next merge window.
next prev parent reply other threads:[~2022-02-22 13:38 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
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 [this message]
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=YhTnSwmHVRe5AzJQ@casper.infradead.org \
--to=willy@infradead.org \
--cc=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 \
/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).