From: David Sterba <dsterba@suse.cz>
To: fdmanana@kernel.org
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH 0/2] fstests: a couple fixes for btrfs/254
Date: Wed, 19 Feb 2025 23:13:34 +0100 [thread overview]
Message-ID: <20250219221334.GG5777@twin.jikos.cz> (raw)
In-Reply-To: <cover.1739989076.git.fdmanana@suse.com>
On Wed, Feb 19, 2025 at 06:19:13PM +0000, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> Fixes for btrfs/254, details in the change logs.
>
> Filipe Manana (2):
> btrfs/254: don't leave mount on test fs in case of failure/interruption
> btrfs/254: fix test failure in case scratch devices are larger than 50G
Reviewed-by: David Sterba <dsterba@suse.com>
next prev parent reply other threads:[~2025-02-19 22:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 18:19 [PATCH 0/2] fstests: a couple fixes for btrfs/254 fdmanana
2025-02-19 18:19 ` [PATCH 1/2] btrfs/254: don't leave mount on test fs in case of failure/interruption fdmanana
2025-02-20 5:27 ` Anand Jain
2025-02-20 17:03 ` Darrick J. Wong
2025-02-20 18:22 ` Filipe Manana
2025-02-21 1:48 ` Anand Jain
2025-02-21 6:09 ` Zorro Lang
2025-02-21 4:18 ` Darrick J. Wong
2025-02-21 6:02 ` Zorro Lang
2025-02-21 20:22 ` Darrick J. Wong
2025-02-25 22:19 ` [PATCH] fstests: finish UMOUNT_PROG to _unmount conversion Dave Chinner
2025-02-26 10:37 ` Filipe Manana
2025-02-26 16:16 ` Darrick J. Wong
2025-02-26 21:37 ` Dave Chinner
2025-02-19 18:19 ` [PATCH 2/2] btrfs/254: fix test failure in case scratch devices are larger than 50G fdmanana
2025-02-20 6:45 ` Anand Jain
2025-02-19 22:13 ` David Sterba [this message]
2025-02-20 6:42 ` [PATCH 0/2] fstests: a couple fixes for btrfs/254 Qu Wenruo
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=20250219221334.GG5777@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--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