From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, willy@infradead.org, tytso@mit.edu,
mark@fasheh.com, joseph.qi@linux.alibaba.com, jlbec@evilplan.org,
jack@suse.cz, almaz.alexandrovich@paragon-software.com,
hch@lst.de, akpm@linux-foundation.org
Subject: [merged mm-stable] ocfs2-use-filemap_fdatawrite_wbc-instead-of-generic_writepages.patch removed from -mm tree
Date: Wed, 18 Jan 2023 17:15:44 -0800 [thread overview]
Message-ID: <20230119011545.0A458C433F0@smtp.kernel.org> (raw)
The quilt patch titled
Subject: ocfs2: use filemap_fdatawrite_wbc instead of generic_writepages
has been removed from the -mm tree. Its filename was
ocfs2-use-filemap_fdatawrite_wbc-instead-of-generic_writepages.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Christoph Hellwig <hch@lst.de>
Subject: ocfs2: use filemap_fdatawrite_wbc instead of generic_writepages
Date: Thu, 29 Dec 2022 06:10:30 -1000
filemap_fdatawrite_wbc is a fairly thing wrapper around do_writepages, and
the big difference there is support for cgroup writeback, which is not
supported by ocfs2, and the potential to use ->writepages instead of
->writepage, which ocfs2 does not currently implement but eventually
should.
Link: https://lkml.kernel.org/r/20221229161031.391878-6-hch@lst.de
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Jan Kara <jack@suse.cz>
Cc: Joel Becker <jlbec@evilplan.org>
Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: Mark Fasheh <mark@fasheh.com>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/ocfs2/journal.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/fs/ocfs2/journal.c~ocfs2-use-filemap_fdatawrite_wbc-instead-of-generic_writepages
+++ a/fs/ocfs2/journal.c
@@ -852,7 +852,7 @@ static int ocfs2_journal_submit_inode_da
.range_end = jinode->i_dirty_end,
};
- return generic_writepages(mapping, &wbc);
+ return filemap_fdatawrite_wbc(mapping, &wbc);
}
int ocfs2_journal_init(struct ocfs2_super *osb, int *dirty)
_
Patches currently in -mm which might be from hch@lst.de are
reply other threads:[~2023-01-19 1:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230119011545.0A458C433F0@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=mm-commits@vger.kernel.org \
--cc=tytso@mit.edu \
--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.