From: Anand Jain <anand.jain@oracle.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Anand Jain <anand.jain@oracle.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: add extent-tree-v2 support to dump-super
Date: Mon, 10 Oct 2022 15:43:51 +0800 [thread overview]
Message-ID: <af541998-3980-85c3-e3c3-dd0cf09f52cf@oracle.com> (raw)
In-Reply-To: <764d5754-62bf-232a-a6c2-67724111a72b@gmx.com>
On 10/9/22 07:13, Qu Wenruo wrote:
>
>
> On 2022/10/8 17:02, Anand Jain wrote:
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>> kernel-shared/print-tree.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/kernel-shared/print-tree.c b/kernel-shared/print-tree.c
>> index 5c3d14298b58..6b5fd37ab2bc 100644
>> --- a/kernel-shared/print-tree.c
>> +++ b/kernel-shared/print-tree.c
>> @@ -1689,6 +1689,9 @@ static struct readable_flag_entry
>> incompat_flags_array[] = {
>> DEF_INCOMPAT_FLAG_ENTRY(METADATA_UUID),
>> DEF_INCOMPAT_FLAG_ENTRY(RAID1C34),
>> DEF_INCOMPAT_FLAG_ENTRY(ZONED),
>> +#if EXPERIMENTAL
>> + DEF_INCOMPAT_FLAG_ENTRY(EXTENT_TREE_V2),
>> +#endif
>
> That's in fact one solution I want to go.
>
> But later I found that, we can enhance __print_readable_flag() to
> iterate the incompat_flags_array[] with extra check on @supported_flags,
> so we can skip the EXPERIMENTAL macro inside the array.
>
> By that, we can reduce the number of EXPERIMENTAL macros, which I
> believe is already causing burdens for testing.
Yeah, possible. However, it is a cleanup; I wouldn't mix that in the bug
fix, here.
Thanks, Anand
>
> Thanks,
> Qu
>> };
>> static const int incompat_flags_num = sizeof(incompat_flags_array) /
>> sizeof(struct readable_flag_entry);
next prev parent reply other threads:[~2022-10-10 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 9:02 [PATCH] btrfs-progs: add extent-tree-v2 support to dump-super Anand Jain
2022-10-08 23:13 ` Qu Wenruo
2022-10-10 7:43 ` Anand Jain [this message]
2022-10-10 20:19 ` 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=af541998-3980-85c3-e3c3-dd0cf09f52cf@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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