From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 00/14] Another batch of inode vs btrfs_inode cleanups
Date: Mon, 2 Nov 2020 16:48:52 +0200 [thread overview]
Message-ID: <20201102144906.3767963-1-nborisov@suse.com> (raw)
Here is another batch which gets use closer to unified btrfs_inode vs inode
usage in functions.
Nikolay Borisov (14):
btrfs: Make btrfs_inode_safe_disk_i_size_write take btrfs_inode
btrfs: Make insert_prealloc_file_extent take btrfs_inode
btrfs: Make btrfs_truncate_inode_items take btrfs_inode
btrfs: Make btrfs_finish_ordered_io btrfs_inode-centric
btrfs: Make btrfs_delayed_update_inode take btrfs_inode
btrfs: Make btrfs_update_inode_item take btrfs_inode
btrfs: Make btrfs_update_inode take btrfs_inode
btrfs: Make maybe_insert_hole take btrfs_inode
btrfs: Make find_first_non_hole take btrfs_inode
btrfs: Make btrfs_insert_replace_extent take btrfs_inode
btrfs: Make btrfs_truncate_block take btrfs_inode
btrfs: Make btrfs_cont_expand take btrfs_inode
btrfs: Make btrfs_drop_extents take btrfs_inode
btrfs: Make btrfs_update_inode_fallback take btrfs_inode
fs/btrfs/block-group.c | 2 +-
fs/btrfs/ctree.h | 21 +--
fs/btrfs/delayed-inode.c | 13 +-
fs/btrfs/delayed-inode.h | 3 +-
fs/btrfs/file-item.c | 18 +--
fs/btrfs/file.c | 88 +++++++------
fs/btrfs/free-space-cache.c | 8 +-
fs/btrfs/inode-map.c | 2 +-
fs/btrfs/inode.c | 249 ++++++++++++++++++------------------
fs/btrfs/ioctl.c | 6 +-
fs/btrfs/reflink.c | 9 +-
fs/btrfs/transaction.c | 3 +-
fs/btrfs/tree-log.c | 24 ++--
fs/btrfs/xattr.c | 4 +-
14 files changed, 233 insertions(+), 217 deletions(-)
--
2.25.1
next reply other threads:[~2020-11-02 14:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 14:48 Nikolay Borisov [this message]
2020-11-02 14:48 ` [PATCH 01/14] btrfs: Make btrfs_inode_safe_disk_i_size_write take btrfs_inode Nikolay Borisov
2020-11-02 14:48 ` [PATCH 02/14] btrfs: Make insert_prealloc_file_extent " Nikolay Borisov
2020-11-02 14:48 ` [PATCH 03/14] btrfs: Make btrfs_truncate_inode_items " Nikolay Borisov
2020-11-05 14:45 ` David Sterba
2020-11-02 14:48 ` [PATCH 04/14] btrfs: Make btrfs_finish_ordered_io btrfs_inode-centric Nikolay Borisov
2020-11-02 14:48 ` [PATCH 05/14] btrfs: Make btrfs_delayed_update_inode take btrfs_inode Nikolay Borisov
2020-11-02 14:48 ` [PATCH 06/14] btrfs: Make btrfs_update_inode_item " Nikolay Borisov
2020-11-02 14:48 ` [PATCH 07/14] btrfs: Make btrfs_update_inode " Nikolay Borisov
2020-11-02 14:49 ` [PATCH 08/14] btrfs: Make maybe_insert_hole " Nikolay Borisov
2020-11-02 14:49 ` [PATCH 09/14] btrfs: Make find_first_non_hole " Nikolay Borisov
2020-11-02 14:49 ` [PATCH 10/14] btrfs: Make btrfs_insert_replace_extent " Nikolay Borisov
2020-11-02 14:49 ` [PATCH 11/14] btrfs: Make btrfs_truncate_block " Nikolay Borisov
2020-11-02 14:49 ` [PATCH 12/14] btrfs: Make btrfs_cont_expand " Nikolay Borisov
2020-11-02 14:49 ` [PATCH 13/14] btrfs: Make btrfs_drop_extents " Nikolay Borisov
2020-11-02 14:49 ` [PATCH 14/14] btrfs: Make btrfs_update_inode_fallback " Nikolay Borisov
2020-11-02 15:48 ` [PATCH 00/14] Another batch of inode vs btrfs_inode cleanups Johannes Thumshirn
2020-11-02 16:10 ` David Sterba
2020-11-02 16:25 ` Johannes Thumshirn
2020-11-05 16:21 ` David Sterba
2020-11-12 18:25 ` 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=20201102144906.3767963-1-nborisov@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.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 NNTP newsgroup(s).