From: Christoph Hellwig <hch@lst.de>
To: Andrew Morton <akpm@linux-foundation.org>,
Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
Joseph Qi <joseph.qi@linux.alibaba.com>,
Evgeniy Dushistov <dushistov@mail.ru>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: ocfs2-devel@oss.oracle.com, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: remove most callers of write_one_page v3
Date: Wed, 18 Jan 2023 18:30:20 +0100 [thread overview]
Message-ID: <20230118173027.294869-1-hch@lst.de> (raw)
Hi all,
this series removes most users of the write_one_page API. These helpers
internally call ->writepage which we are gradually removing from the
kernel.
Changes since v2:
- more minix error handling fixes
Changes since v1:
- drop the btrfs changes (queue up in the btrfs tree)
- drop the finaly move to jfs (can't be done without the btrfs patches)
- fix the existing minix code to properly propagate errors
Diffstat:
minix/dir.c | 62 +++++++++++++++++++++++++++------------------------
minix/minix.h | 3 +-
minix/namei.c | 27 ++++++++++++----------
ocfs2/refcounttree.c | 9 ++++---
sysv/dir.c | 30 +++++++++++++++---------
ufs/dir.c | 29 +++++++++++++++--------
6 files changed, 94 insertions(+), 66 deletions(-)
next reply other threads:[~2023-01-18 17:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 17:30 Christoph Hellwig [this message]
2023-01-18 17:30 ` [PATCH 1/7] minix: move releasing pages into unlink and rename Christoph Hellwig
2023-01-18 17:30 ` [PATCH 2/7] minix: fix error handling in minix_delete_entry Christoph Hellwig
2023-01-18 17:30 ` [PATCH 3/7] minix: fix error handling in minix_set_link Christoph Hellwig
2023-01-18 17:30 ` [PATCH 4/7] minix: don't flush page immediately for DIRSYNC directories Christoph Hellwig
2023-01-18 17:30 ` [PATCH 5/7] sysv: " Christoph Hellwig
2023-01-18 17:30 ` [PATCH 6/7] ufs: " Christoph Hellwig
2023-01-18 17:30 ` [PATCH 7/7] ocfs2: don't use write_one_page in ocfs2_duplicate_clusters_by_page Christoph Hellwig
2023-01-18 21:09 ` remove most callers of write_one_page v3 Andrew Morton
2023-01-18 21:23 ` Al Viro
2023-01-18 21:33 ` Al Viro
2023-01-19 5:28 ` Christoph Hellwig
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=20230118173027.294869-1-hch@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=dushistov@mail.ru \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@oss.oracle.com \
--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