From: patchwork-bot+f2fs@kernel.org
To: Christoph Hellwig <hch@lst.de>
Cc: willy@infradead.org, djwong@kernel.org, linux-mm@kvack.org,
agruenba@redhat.com, miklos@szeredi.hu, cluster-devel@redhat.com,
idryomov@gmail.com, linux-ext4@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-block@vger.kernel.org,
dlemoal@kernel.org, viro@zeniv.linux.org.uk, jaegeuk@kernel.org,
ceph-devel@vger.kernel.org, xiubli@redhat.com,
trond.myklebust@hammerspace.com, axboe@kernel.dk,
brauner@kernel.org, tytso@mit.edu, johannes.thumshirn@wdc.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, anna@kernel.org,
linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org,
hare@suse.de
Subject: Re: [f2fs-dev] [PATCH 01/12] backing_dev: remove current->backing_dev_info
Date: Thu, 06 Jul 2023 00:18:14 +0000 [thread overview]
Message-ID: <168860269459.29151.8627542432532930093.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230601145904.1385409-2-hch@lst.de>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Andrew Morton <akpm@linux-foundation.org>:
On Thu, 1 Jun 2023 16:58:53 +0200 you wrote:
> The last user of current->backing_dev_info disappeared in commit
> b9b1335e6403 ("remove bdi_congested() and wb_congested() and related
> functions"). Remove the field and all assignments to it.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Christian Brauner <brauner@kernel.org>
> Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
> Reviewed-by: Hannes Reinecke <hare@suse.de>
> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> Reviewed-by: Darrick J. Wong <djwong@kernel.org>
> Acked-by: Theodore Ts'o <tytso@mit.edu>
>
> [...]
Here is the summary with links:
- [f2fs-dev,01/12] backing_dev: remove current->backing_dev_info
https://git.kernel.org/jaegeuk/f2fs/c/0d625446d0a4
- [f2fs-dev,02/12] iomap: update ki_pos a little later in iomap_dio_complete
https://git.kernel.org/jaegeuk/f2fs/c/936e114a245b
- [f2fs-dev,03/12] filemap: update ki_pos in generic_perform_write
https://git.kernel.org/jaegeuk/f2fs/c/182c25e9c157
- [f2fs-dev,04/12] filemap: add a kiocb_write_and_wait helper
https://git.kernel.org/jaegeuk/f2fs/c/3c435a0fe35c
- [f2fs-dev,05/12] filemap: add a kiocb_invalidate_pages helper
https://git.kernel.org/jaegeuk/f2fs/c/e003f74afbd2
- [f2fs-dev,06/12] filemap: add a kiocb_invalidate_post_direct_write helper
https://git.kernel.org/jaegeuk/f2fs/c/c402a9a9430b
- [f2fs-dev,07/12] iomap: update ki_pos in iomap_file_buffered_write
https://git.kernel.org/jaegeuk/f2fs/c/219580eea1ee
- [f2fs-dev,08/12] iomap: use kiocb_write_and_wait and kiocb_invalidate_pages
https://git.kernel.org/jaegeuk/f2fs/c/8ee93b4bb626
- [f2fs-dev,09/12] fs: factor out a direct_write_fallback helper
https://git.kernel.org/jaegeuk/f2fs/c/44fff0fa08ec
- [f2fs-dev,10/12] fuse: update ki_pos in fuse_perform_write
https://git.kernel.org/jaegeuk/f2fs/c/70e986c3b4f4
- [f2fs-dev,11/12] fuse: drop redundant arguments to fuse_perform_write
https://git.kernel.org/jaegeuk/f2fs/c/596df33d673d
- [f2fs-dev,12/12] fuse: use direct_write_fallback
https://git.kernel.org/jaegeuk/f2fs/c/64d1b4dd826d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
parent reply other threads:[~2023-07-06 0:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230601145904.1385409-2-hch@lst.de>]
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=168860269459.29151.8627542432532930093.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=agruenba@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anna@kernel.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=cluster-devel@redhat.com \
--cc=djwong@kernel.org \
--cc=dlemoal@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=idryomov@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--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-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=trond.myklebust@hammerspace.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=xiubli@redhat.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