From: patchwork-bot+f2fs@kernel.org
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, cluster-devel@redhat.com,
linux-nfs@vger.kernel.org, miklos@szeredi.hu, djwong@kernel.org,
ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
willy@infradead.org, linux-f2fs-devel@lists.sourceforge.net,
linux-block@vger.kernel.org, linux-mm@kvack.org,
dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
akpm@linux-foundation.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [Cluster-devel] [f2fs-dev] [PATCH 01/17] fs: unexport buffer_check_dirty_writeback
Date: Mon, 04 Sep 2023 18:11:08 +0000 [thread overview]
Message-ID: <169385106874.19669.13506137748616735375.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230424054926.26927-2-hch@lst.de>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jens Axboe <axboe@kernel.dk>:
On Mon, 24 Apr 2023 07:49:10 +0200 you wrote:
> buffer_check_dirty_writeback is only used by the block device aops,
> remove the export.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/buffer.c | 1 -
> 1 file changed, 1 deletion(-)
Here is the summary with links:
- [f2fs-dev,01/17] fs: unexport buffer_check_dirty_writeback
(no matching commit)
- [f2fs-dev,02/17] fs: remove the special !CONFIG_BLOCK def_blk_fops
(no matching commit)
- [f2fs-dev,03/17] fs: rename and move block_page_mkwrite_return
(no matching commit)
- [f2fs-dev,04/17] fs: remove emergency_thaw_bdev
https://git.kernel.org/jaegeuk/f2fs/c/4a8b719f95c0
- [f2fs-dev,05/17] filemap: update ki_pos in generic_perform_write
(no matching commit)
- [f2fs-dev,06/17] filemap: add a kiocb_write_and_wait helper
(no matching commit)
- [f2fs-dev,07/17] filemap: add a kiocb_invalidate_pages helper
(no matching commit)
- [f2fs-dev,08/17] filemap: add a kiocb_invalidate_post_write helper
(no matching commit)
- [f2fs-dev,09/17] fs: factor out a direct_write_fallback helper
(no matching commit)
- [f2fs-dev,10/17] iomap: use kiocb_write_and_wait and kiocb_invalidate_pages
(no matching commit)
- [f2fs-dev,11/17] iomap: assign current->backing_dev_info in iomap_file_buffered_write
(no matching commit)
- [f2fs-dev,12/17] fuse: use direct_write_fallback
(no matching commit)
- [f2fs-dev,13/17] block: don't plug in blkdev_write_iter
(no matching commit)
- [f2fs-dev,14/17] block: open code __generic_file_write_iter for blkdev writes
(no matching commit)
- [f2fs-dev,15/17] block: stop setting ->direct_IO
(no matching commit)
- [f2fs-dev,16/17] block: use iomap for writes to block devices
(no matching commit)
- [f2fs-dev,17/17] fs: add CONFIG_BUFFER_HEAD
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-09-04 18:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 5:49 [Cluster-devel] RFC: allow building a kernel without buffer_heads Christoph Hellwig
2023-04-24 5:49 ` [Cluster-devel] [PATCH 01/17] fs: unexport buffer_check_dirty_writeback Christoph Hellwig
2023-05-19 14:17 ` Hannes Reinecke
2023-07-06 0:18 ` [Cluster-devel] [f2fs-dev] " patchwork-bot+f2fs
2023-09-04 18:11 ` patchwork-bot+f2fs [this message]
2023-04-24 5:49 ` [Cluster-devel] [PATCH 02/17] fs: remove the special !CONFIG_BLOCK def_blk_fops Christoph Hellwig
2023-04-24 19:22 ` Randy Dunlap
2023-04-24 19:37 ` Keith Busch
2023-04-24 5:49 ` [Cluster-devel] [PATCH 03/17] fs: rename and move block_page_mkwrite_return Christoph Hellwig
2023-04-24 12:30 ` Matthew Wilcox
2023-04-24 12:42 ` Christoph Hellwig
2023-04-24 5:49 ` [Cluster-devel] [PATCH 04/17] fs: remove emergency_thaw_bdev Christoph Hellwig
2023-04-24 5:49 ` [Cluster-devel] [PATCH 05/17] filemap: update ki_pos in generic_perform_write Christoph Hellwig
2023-04-24 18:54 ` Andreas Gruenbacher
2023-04-24 5:49 ` [Cluster-devel] [PATCH 06/17] filemap: add a kiocb_write_and_wait helper Christoph Hellwig
2023-04-24 5:49 ` [Cluster-devel] [PATCH 07/17] filemap: add a kiocb_invalidate_pages helper Christoph Hellwig
2023-04-24 5:49 ` [Cluster-devel] [PATCH 08/17] filemap: add a kiocb_invalidate_post_write helper Christoph Hellwig
2023-04-24 5:49 ` [Cluster-devel] [PATCH 09/17] fs: factor out a direct_write_fallback helper Christoph Hellwig
2023-04-24 5:49 ` [Cluster-devel] [PATCH 10/17] iomap: use kiocb_write_and_wait and kiocb_invalidate_pages Christoph Hellwig
2023-04-24 5:49 ` [Cluster-devel] [PATCH 11/17] iomap: assign current->backing_dev_info in iomap_file_buffered_write Christoph Hellwig
2023-04-24 6:18 ` Darrick J. Wong
2023-04-24 6:22 ` Christoph Hellwig
2023-04-24 5:49 ` [Cluster-devel] [PATCH 12/17] fuse: use direct_write_fallback Christoph Hellwig
2023-04-24 5:49 ` [Cluster-devel] [PATCH 13/17] block: don't plug in blkdev_write_iter Christoph Hellwig
2023-04-24 5:49 ` [Cluster-devel] [PATCH 14/17] block: open code __generic_file_write_iter for blkdev writes Christoph Hellwig
2023-05-24 22:23 ` Luis Chamberlain
2023-04-24 5:49 ` [Cluster-devel] [PATCH 15/17] block: stop setting ->direct_IO Christoph Hellwig
2023-04-24 5:49 ` [Cluster-devel] [PATCH 16/17] block: use iomap for writes to block devices Christoph Hellwig
[not found] ` <CGME20230426130921eucas1p279078812be7e8d50c1305e47cea53661@eucas1p2.samsung.com>
2023-04-26 13:00 ` [Cluster-devel] [f2fs-dev] " Pankaj Raghav
2023-05-19 14:22 ` [Cluster-devel] " Hannes Reinecke
2023-05-23 22:27 ` Dave Chinner
2023-05-24 13:33 ` Matthew Wilcox
2023-07-20 12:09 ` Christoph Hellwig
2023-07-20 12:06 ` Christoph Hellwig
2023-07-20 12:16 ` Hannes Reinecke
2023-04-24 5:49 ` [Cluster-devel] [PATCH 17/17] fs: add CONFIG_BUFFER_HEAD Christoph Hellwig
2023-04-29 0:11 ` Luis Chamberlain
2023-04-29 1:20 ` Matthew Wilcox
2023-05-01 3:14 ` Luis Chamberlain
2023-05-01 15:46 ` Matthew Wilcox
2023-05-01 16:00 ` Pankaj Raghav
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=169385106874.19669.13506137748616735375.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=ceph-devel@vger.kernel.org \
--cc=cluster-devel@redhat.com \
--cc=dhowells@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).