From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 4/4] iomap: remove iomap_writepage
Date: Mon, 11 Jul 2022 13:48:07 +0900 [thread overview]
Message-ID: <ae8f3075-f13e-1ce6-4bdd-86926cf3ded2@opensource.wdc.com> (raw)
In-Reply-To: <20220711041459.1062583-5-hch@lst.de>
On 7/11/22 13:14, Christoph Hellwig wrote:
> Unused now.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/iomap/buffered-io.c | 15 ---------------
> include/linux/iomap.h | 3 ---
> 2 files changed, 18 deletions(-)
>
> diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
> index d2a9f699e17ed..1bac8bda40d0c 100644
> --- a/fs/iomap/buffered-io.c
> +++ b/fs/iomap/buffered-io.c
> @@ -1518,21 +1518,6 @@ iomap_do_writepage(struct page *page, struct writeback_control *wbc, void *data)
> return 0;
> }
>
> -int
> -iomap_writepage(struct page *page, struct writeback_control *wbc,
> - struct iomap_writepage_ctx *wpc,
> - const struct iomap_writeback_ops *ops)
> -{
> - int ret;
> -
> - wpc->ops = ops;
> - ret = iomap_do_writepage(page, wbc, wpc);
> - if (!wpc->ioend)
> - return ret;
> - return iomap_submit_ioend(wpc, wpc->ioend, ret);
> -}
> -EXPORT_SYMBOL_GPL(iomap_writepage);
> -
> int
> iomap_writepages(struct address_space *mapping, struct writeback_control *wbc,
> struct iomap_writepage_ctx *wpc,
> diff --git a/include/linux/iomap.h b/include/linux/iomap.h
> index e552097c67e0b..911888560d3eb 100644
> --- a/include/linux/iomap.h
> +++ b/include/linux/iomap.h
> @@ -303,9 +303,6 @@ void iomap_finish_ioends(struct iomap_ioend *ioend, int error);
> void iomap_ioend_try_merge(struct iomap_ioend *ioend,
> struct list_head *more_ioends);
> void iomap_sort_ioends(struct list_head *ioend_list);
> -int iomap_writepage(struct page *page, struct writeback_control *wbc,
> - struct iomap_writepage_ctx *wpc,
> - const struct iomap_writeback_ops *ops);
> int iomap_writepages(struct address_space *mapping,
> struct writeback_control *wbc, struct iomap_writepage_ctx *wpc,
> const struct iomap_writeback_ops *ops);
Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-07-11 4:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 4:14 [Cluster-devel] remove iomap_writepage Christoph Hellwig
2022-07-11 4:14 ` [Cluster-devel] [PATCH 1/4] gfs2: stop using generic_writepages in gfs2_ail1_start_one Christoph Hellwig
2022-07-11 10:27 ` Andreas Gruenbacher
2022-07-11 14:30 ` Christoph Hellwig
2022-07-11 4:14 ` [Cluster-devel] [PATCH 2/4] gfs2: remove ->writepage Christoph Hellwig
2022-07-11 23:22 ` Andreas Grünbacher
2022-07-12 4:57 ` Christoph Hellwig
2022-07-11 4:14 ` [Cluster-devel] [PATCH 3/4] zonefs: " Christoph Hellwig
2022-07-11 4:47 ` Damien Le Moal
2022-07-11 9:12 ` Johannes Thumshirn
2022-07-11 4:14 ` [Cluster-devel] [PATCH 4/4] iomap: remove iomap_writepage Christoph Hellwig
2022-07-11 4:48 ` Damien Le Moal [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-19 4:13 [Cluster-devel] remove iomap_writepage v2 Christoph Hellwig
2022-07-19 4:13 ` [Cluster-devel] [PATCH 4/4] iomap: remove iomap_writepage Christoph Hellwig
2022-07-19 6:56 ` Chaitanya Kulkarni
2022-07-22 17:56 ` Darrick J. Wong
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=ae8f3075-f13e-1ce6-4bdd-86926cf3ded2@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
/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;
as well as URLs for NNTP newsgroup(s).