From: Christoph Hellwig <hch@lst.de>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@lst.de>,
Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.com>,
Dave Kleikamp <shaggy@kernel.org>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
jfs-discussion@lists.sourceforge.net
Subject: Re: [PATCH 5/5] fs: remove the NULL get_block case in mpage_writepages
Date: Fri, 10 Jun 2022 10:00:32 +0200 [thread overview]
Message-ID: <20220610080032.GA29310@lst.de> (raw)
In-Reply-To: <20220609172530.q7bzttn5v2orirre@quack3.lan>
On Thu, Jun 09, 2022 at 07:25:30PM +0200, Jan Kara wrote:
> On Wed 08-06-22 17:04:51, Christoph Hellwig wrote:
> > No one calls mpage_writepages with a NULL get_block paramter, so remove
> > support for that case.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> What about ntfs_writepages()? That seems to call mpage_writepages() with
> NULL get_block() in one case...
Oops, yeah.
prev parent reply other threads:[~2022-06-10 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 15:04 remove the nobh helpers Christoph Hellwig
2022-06-08 15:04 ` [PATCH 1/5] ext2: remove nobh support Christoph Hellwig
2022-06-08 16:39 ` Matthew Wilcox
2022-06-09 3:54 ` Christoph Hellwig
2022-06-09 17:32 ` Jan Kara
2022-06-08 15:04 ` [PATCH 2/5] jfs: stop using the nobh helper Christoph Hellwig
2022-06-08 15:04 ` [PATCH 3/5] fs: remove the nobh helpers Christoph Hellwig
2022-06-09 17:33 ` Jan Kara
2022-06-08 15:04 ` [PATCH 4/5] fs: don't call ->writepage from __mpage_writepage Christoph Hellwig
2022-06-09 17:31 ` Jan Kara
2022-06-10 8:00 ` Christoph Hellwig
2022-06-08 15:04 ` [PATCH 5/5] fs: remove the NULL get_block case in mpage_writepages Christoph Hellwig
2022-06-09 17:25 ` Jan Kara
2022-06-10 8:00 ` Christoph Hellwig [this message]
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=20220610080032.GA29310@lst.de \
--to=hch@lst.de \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@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.