From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] btrfs-progs: cleanup related to btrfs super block
Date: Thu, 4 Nov 2021 20:10:17 +0100 [thread overview]
Message-ID: <20211104191017.GD28560@twin.jikos.cz> (raw)
In-Reply-To: <20211021014020.482242-1-wqu@suse.com>
On Thu, Oct 21, 2021 at 09:40:17AM +0800, Qu Wenruo wrote:
> This patchset mostly cleans up the mismatch between
> BTRFS_SUPER_INFO_SIZE and sizeof(struct btrfs_super_block).
>
> This cleanup itself is going to replace all the following snippets:
>
> u8 super_block_data[BTRFS_SUPER_INFO_SIZE];
> struct btrfs_super_block *sb;
>
> sb = (struct btrfs_super_block *)super_block_data;
>
> With:
>
> struct btrfs_super_block sb;
>
> Also since we're here, also cache csum_type and csum_size in fs_info,
> just like what we did in the kernel.
>
> Qu Wenruo (3):
> btrfs-progs: unify sizeof(struct btrfs_super_block) and
> BTRFS_SUPER_INFO_SIZE
> btrfs-progs: remove temporary buffer for super block
> btrfs-progs: cache csum_size and csum_type in btrfs_fs_info
Added to devel, thanks, the removal of temporary buffer for superblock
is nice.
prev parent reply other threads:[~2021-11-04 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 1:40 [PATCH 0/3] btrfs-progs: cleanup related to btrfs super block Qu Wenruo
2021-10-21 1:40 ` [PATCH 1/3] btrfs-progs: unify sizeof(struct btrfs_super_block) and BTRFS_SUPER_INFO_SIZE Qu Wenruo
2021-10-21 12:40 ` David Sterba
2021-10-21 12:49 ` Qu Wenruo
2021-10-21 1:40 ` [PATCH 2/3] btrfs-progs: remove temporary buffer for super block Qu Wenruo
2021-10-21 1:40 ` [PATCH 3/3] btrfs-progs: cache csum_size and csum_type in btrfs_fs_info Qu Wenruo
2021-11-04 19:10 ` David Sterba [this message]
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=20211104191017.GD28560@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@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