From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: David Sterba <dsterba@suse.cz>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] 3 small cleanups for find_first_block_group
Date: Fri, 29 May 2020 14:25:32 +0000 [thread overview]
Message-ID: <SN4PR0401MB3598731CEEA486E8601766999B8F0@SN4PR0401MB3598.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200527081227.3408-1-johannes.thumshirn@wdc.com
On 27/05/2020 10:12, Johannes Thumshirn wrote:
> While trying to learn the Block Group code I've found some cleanup
> possibilities for find_first_block_group().
>
> Here's a proposal to make $ffbg a bit more easier to read by untangling the
> gotos and if statements.
>
> The patch set is based on misc-next from May 26 morning with
> HEAD 3f4a266717ed ("btrfs: split btrfs_direct_IO to read and write part")
> and xfstests showed no regressions to the base misc-next in my test setup.
>
> Changes to v1:
> - Pass btrfs_path instead of leaf & slot to read_bg_from_eb (Nikolay)
> - Don't comment about the size change (Nikolay)
> - Add Nikolay's Reviewed-by's
>
> Johannes Thumshirn (3):
> btrfs: remove pointless out label in find_first_block_group
> btrfs: get mapping tree directly from fsinfo in find_first_block_group
> btrfs: factor out reading of bg from find_frist_block_group
>
> fs/btrfs/block-group.c | 108 ++++++++++++++++++++++-------------------
> 1 file changed, 58 insertions(+), 50 deletions(-)
>
David, any comment if you will consider this series? Patch 2/3 actually makes
the function more complainant to the kernel's coding style.
next prev parent reply other threads:[~2020-05-29 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 8:12 [PATCH v2 0/3] 3 small cleanups for find_first_block_group Johannes Thumshirn
2020-05-27 8:12 ` [PATCH v2 1/3] btrfs: remove pointless out label in find_first_block_group Johannes Thumshirn
2020-05-27 13:06 ` David Sterba
2020-05-27 13:45 ` Johannes Thumshirn
2020-06-01 15:34 ` David Sterba
2020-05-27 8:12 ` [PATCH v2 2/3] btrfs: get mapping tree directly from fsinfo " Johannes Thumshirn
2020-05-27 8:12 ` [PATCH v2 3/3] btrfs: factor out reading of bg from find_frist_block_group Johannes Thumshirn
2020-05-29 14:25 ` Johannes Thumshirn [this message]
2020-06-01 15:48 ` [PATCH v2 0/3] 3 small cleanups for find_first_block_group 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=SN4PR0401MB3598731CEEA486E8601766999B8F0@SN4PR0401MB3598.namprd04.prod.outlook.com \
--to=johannes.thumshirn@wdc.com \
--cc=dsterba@suse.cz \
--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).