[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251014045325.GD30978@lst.de>
Date: Tue, 14 Oct 2025 06:53:25 +0200
From: Christoph Hellwig <hch@....de>
To: Jan Kara <jack@...e.cz>
Cc: Christoph Hellwig <hch@....de>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
Eric Van Hensbergen <ericvh@...nel.org>,
Latchesar Ionkov <lucho@...kov.net>,
Dominique Martinet <asmadeus@...ewreck.org>,
Christian Schoenebeck <linux_oss@...debyte.com>,
Chris Mason <clm@...com>, David Sterba <dsterba@...e.com>,
Mark Fasheh <mark@...heh.com>, Joel Becker <jlbec@...lplan.org>,
Joseph Qi <joseph.qi@...ux.alibaba.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
Josef Bacik <josef@...icpanda.com>, linux-block@...r.kernel.org,
v9fs@...ts.linux.dev, linux-btrfs@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
jfs-discussion@...ts.sourceforge.net, ocfs2-devel@...ts.linux.dev,
linux-xfs@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH 07/10] mm: remove __filemap_fdatawrite
On Mon, Oct 13, 2025 at 01:59:21PM +0200, Jan Kara wrote:
> > - return __filemap_fdatawrite(mapping, WB_SYNC_NONE);
> > + return filemap_fdatawrite_range_kick(mapping, 0, LLONG_MAX);
> > }
> > EXPORT_SYMBOL(filemap_flush);
>
> filemap_fdatawrite_range_kick() doesn't exist at this point in the series.
It does exist even in the current upstream kernel.
filemap_fdatawrite_kick doesn't exist yet.
Powered by blists - more mailing lists