From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/4] f2fs: Remove check for ->writepage
Date: Tue, 11 Mar 2025 19:48:48 +0800 [thread overview]
Message-ID: <9562210b-bf6e-4bbc-860f-40aec418ea36@kernel.org> (raw)
In-Reply-To: <20250307182151.3397003-2-willy@infradead.org>
On 3/8/25 02:21, Matthew Wilcox (Oracle) wrote:
> We're almost able to remove a_ops->writepage. This check is unnecessary
> as we'll never call into __f2fs_write_data_pages() for character
> devices.
>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Jaegeuk Kim <jaegeuk@kernel.org>
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/4] f2fs: Remove check for ->writepage
Date: Tue, 11 Mar 2025 19:48:48 +0800 [thread overview]
Message-ID: <9562210b-bf6e-4bbc-860f-40aec418ea36@kernel.org> (raw)
In-Reply-To: <20250307182151.3397003-2-willy@infradead.org>
On 3/8/25 02:21, Matthew Wilcox (Oracle) wrote:
> We're almost able to remove a_ops->writepage. This check is unnecessary
> as we'll never call into __f2fs_write_data_pages() for character
> devices.
>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2025-03-11 11:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 18:21 [f2fs-dev] [PATCH 0/4] f2fs: Remove uses of writepage Matthew Wilcox (Oracle)
2025-03-07 18:21 ` Matthew Wilcox (Oracle)
2025-03-07 18:21 ` [f2fs-dev] [PATCH 1/4] f2fs: Remove check for ->writepage Matthew Wilcox (Oracle)
2025-03-07 18:21 ` Matthew Wilcox (Oracle)
2025-03-11 11:48 ` Chao Yu via Linux-f2fs-devel [this message]
2025-03-11 11:48 ` Chao Yu
2025-03-07 18:21 ` [f2fs-dev] [PATCH 2/4] f2fs: Remove f2fs_write_data_page() Matthew Wilcox (Oracle)
2025-03-07 18:21 ` Matthew Wilcox (Oracle)
2025-03-11 11:48 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-03-11 11:48 ` Chao Yu
2025-03-07 18:21 ` [f2fs-dev] [PATCH 3/4] f2fs: Remove f2fs_write_meta_page() Matthew Wilcox (Oracle)
2025-03-07 18:21 ` Matthew Wilcox (Oracle)
2025-03-11 11:49 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-03-11 11:49 ` Chao Yu
2025-03-07 18:21 ` [f2fs-dev] [PATCH 4/4] f2fs: Remove f2fs_write_node_page() Matthew Wilcox (Oracle)
2025-03-07 18:21 ` Matthew Wilcox (Oracle)
2025-03-11 11:49 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-03-11 11:49 ` Chao Yu
2025-03-07 20:39 ` [f2fs-dev] [PATCH 0/4] f2fs: Remove uses of writepage Jaegeuk Kim via Linux-f2fs-devel
2025-03-07 20:39 ` Jaegeuk Kim
2025-03-07 20:48 ` [f2fs-dev] " Matthew Wilcox
2025-03-07 20:48 ` Matthew Wilcox
2025-03-07 22:13 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2025-03-07 22:13 ` Jaegeuk Kim
2025-03-11 19:50 ` [f2fs-dev] " patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-11 19:50 ` patchwork-bot+f2fs
2025-03-12 0:18 ` Matthew Wilcox
2025-03-12 0:18 ` Matthew Wilcox
2025-03-12 1:22 ` Jaegeuk Kim via Linux-f2fs-devel
2025-03-12 1:22 ` Jaegeuk Kim
2025-03-14 15:57 ` Matthew Wilcox
2025-03-14 15:57 ` Matthew Wilcox
2025-03-14 21:38 ` Jaegeuk Kim via Linux-f2fs-devel
2025-03-14 21:38 ` Jaegeuk Kim
2025-03-26 3:37 ` Matthew Wilcox
2025-03-26 3:37 ` Matthew Wilcox
2025-03-27 22:27 ` Jaegeuk Kim via Linux-f2fs-devel
2025-03-27 22:27 ` Jaegeuk Kim
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=9562210b-bf6e-4bbc-860f-40aec418ea36@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-fsdevel@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 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.