From: Anand Jain <anand.jain@oracle.com>
To: Zorro Lang <zlang@redhat.com>
Cc: zlang@kernel.org, fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [GIT PULL] fstests: btrfs changes staged-20240418
Date: Mon, 6 May 2024 19:49:03 +0800 [thread overview]
Message-ID: <c2300be9-648b-43fd-be07-6144de35b72f@oracle.com> (raw)
In-Reply-To: <20240424154923.fo526va22bplhaug@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On 4/24/24 23:49, Zorro Lang wrote:
> On Wed, Apr 24, 2024 at 06:06:43AM +0800, Anand Jain wrote:
>> (I just realized that the previous attempt to send this PR failed. Resending it now.)
>>
>> Zorro,
>>
>> Several of the btrfs test cases were failing due to a change in the golden
>> output. The commits here fix them. These patches are on top of the last PR
>> branch staged-20240414.
>
> Hi Anand,
>
> Thanks for working on this! Now I've merged all 12 patches with below changes:
>
> I added your RVB to:
> fstests: btrfs: use _btrfs for 'subvolume snapshot' command
> due to I trust you've reviewed it as you'd like to push it.
>
Yes, it's fine.
> Then I reviewed those 4 patches from you (refer to mail list):
> generic: move btrfs clone device testcase to the generic group
> common/verity: fix btrfs-corrupt-block -v option
> btrfs/290: fix btrfs_corrupt_block options
> common/btrfs: refactor _require_btrfs_corrupt_block to check option
>
> and merged these 4 patches with the review points (to save time).
>
> Please check the "patches-in-queue" branch of upstream fstests. If you
> (or other btrfs folks) feel anything wrong, feel free to tell me. If
> no more changes are needed, you'll see them in next release :)
>
Checked patches in the patches-in-queue; they look good.
Thanks, Anand
> Thanks,
> Zorro
prev parent reply other threads:[~2024-05-06 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 22:06 [GIT PULL] fstests: btrfs changes staged-20240418 Anand Jain
2024-04-24 9:12 ` Zorro Lang
2024-04-24 12:14 ` David Sterba
2024-04-24 14:23 ` Zorro Lang
2024-04-24 15:49 ` Zorro Lang
2024-05-06 11:49 ` Anand Jain [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=c2300be9-648b-43fd-be07-6144de35b72f@oracle.com \
--to=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=zlang@kernel.org \
--cc=zlang@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).