From: Josef Bacik <josef@toxicpanda.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 00/12] Another batch of inode vs btrfs_inode cleanups
Date: Mon, 31 Aug 2020 11:43:34 -0400 [thread overview]
Message-ID: <02f72a45-8f6b-ca9b-d47c-daadb6153da8@toxicpanda.com> (raw)
In-Reply-To: <20200831114249.8360-1-nborisov@suse.com>
On 8/31/20 7:42 AM, Nikolay Borisov wrote:
> Here is the latest batch of inode vs btrfs_inode of interface cleanups for
> internal btrfs functions.
>
> Nikolay Borisov (12):
> btrfs: Make inode_tree_del take btrfs_inode
> btrfs: Make btrfs_lookup_first_ordered_extent take btrfs_inode
> btrfs: Make ordered extent tracepoint take btrfs_inode
> btrfs: Make btrfs_dec_test_ordered_pending take btrfs_inode
> btrfs: Convert btrfs_inode_sectorsize to take btrfs_inode
> btrfs: Make btrfs_invalidatepage work on btrfs_inode
> btrfs: Make btrfs_writepage_endio_finish_ordered btrfs_inode-centric
> btrfs: Make get_extent_skip_holes take btrfs_inode
> btrfs: Make btrfs_find_ordered_sum take btrfs_inode
> btrfs: Make copy_inline_to_page take btrfs_inode
> btrfs: Make btrfs_zero_range_check_range_boundary take btrfs_inode
> btrfs: Make extent_fiemap take btrfs_iode
>
Applied and built against misc-next, spot checked everything, you can add
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
to the whole series, thanks,
Josef
next prev parent reply other threads:[~2020-08-31 15:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 11:42 [PATCH 00/12] Another batch of inode vs btrfs_inode cleanups Nikolay Borisov
2020-08-31 11:42 ` [PATCH 01/12] btrfs: Make inode_tree_del take btrfs_inode Nikolay Borisov
2020-08-31 12:03 ` Johannes Thumshirn
2020-08-31 11:42 ` [PATCH 02/12] btrfs: Make btrfs_lookup_first_ordered_extent " Nikolay Borisov
2020-08-31 12:09 ` Johannes Thumshirn
2020-08-31 11:42 ` [PATCH 03/12] btrfs: Make ordered extent tracepoint " Nikolay Borisov
2020-08-31 12:14 ` Johannes Thumshirn
2020-08-31 11:42 ` [PATCH 04/12] btrfs: Make btrfs_dec_test_ordered_pending " Nikolay Borisov
2020-08-31 12:19 ` Johannes Thumshirn
2020-08-31 11:42 ` [PATCH 05/12] btrfs: Convert btrfs_inode_sectorsize to " Nikolay Borisov
2020-08-31 12:20 ` Johannes Thumshirn
2020-08-31 11:42 ` [PATCH 06/12] btrfs: Make btrfs_invalidatepage work on btrfs_inode Nikolay Borisov
2020-08-31 13:24 ` Johannes Thumshirn
2020-08-31 11:42 ` [PATCH 07/12] btrfs: Make btrfs_writepage_endio_finish_ordered btrfs_inode-centric Nikolay Borisov
2020-08-31 12:23 ` Johannes Thumshirn
2020-08-31 11:42 ` [PATCH 08/12] btrfs: Make get_extent_skip_holes take btrfs_inode Nikolay Borisov
2020-08-31 12:26 ` Johannes Thumshirn
2020-08-31 11:42 ` [PATCH 09/12] btrfs: Make btrfs_find_ordered_sum " Nikolay Borisov
2020-08-31 13:14 ` Johannes Thumshirn
2020-08-31 11:42 ` [PATCH 10/12] btrfs: Make copy_inline_to_page " Nikolay Borisov
2020-08-31 13:18 ` Johannes Thumshirn
2020-08-31 11:42 ` [PATCH 11/12] btrfs: Make btrfs_zero_range_check_range_boundary " Nikolay Borisov
2020-08-31 13:20 ` Johannes Thumshirn
2020-08-31 11:42 ` [PATCH 12/12] btrfs: Make extent_fiemap take btrfs_iode Nikolay Borisov
2020-08-31 13:21 ` Johannes Thumshirn
2020-08-31 15:43 ` Josef Bacik [this message]
2020-09-01 14:13 ` [PATCH 00/12] Another batch of inode vs btrfs_inode cleanups David Sterba
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=02f72a45-8f6b-ca9b-d47c-daadb6153da8@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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