From: Leo Martins <loemra.dev@gmail.com>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com, fstests@vger.kernel.org
Subject: Re: [PATCH v2 3/3] fstests: btrfs: test RAID conversions under stress
Date: Mon, 6 Oct 2025 10:37:51 -0700 [thread overview]
Message-ID: <20251006173757.296087-1-loemra.dev@gmail.com> (raw)
In-Reply-To: <55d549d2-fec1-442f-ad9f-875d2ec6c864@suse.com>
On Sat, 4 Oct 2025 11:24:27 +0930 Qu Wenruo <wqu@suse.com> wrote:
>
>
> 在 2025/10/4 09:11, Leo Martins 写道:
> > Add test to test btrfs conversion while being stressed. This is
> > important since btrfs no longer allows allocating from different RAID
> > block_groups during conversions meaning there may be added enospc
> > pressure.
> >
> > Signed-off-by: Leo Martins <loemra.dev@gmail.com>
>
> Please do not mix patches for different projects into the same patchset.
>
> A lot of us are using b4 to merge (kernel/progs) patches, which will
> merge the whole series, including the one intended to fstests.
>
> Thanks,
> Qu
Got it, sorry about that. Should I resend the patches?
next prev parent reply other threads:[~2025-10-06 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 23:41 [PATCH v2 0/3] btrfs: find_free_extent cleanups Leo Martins
2025-10-03 23:41 ` [PATCH v2 1/3] btrfs: remove ffe RAID loop Leo Martins
2025-10-15 3:29 ` Boris Burkov
2025-10-03 23:41 ` [PATCH v2 2/3] btrfs: add tracing for find_free_extent skip conditions Leo Martins
2025-10-15 3:28 ` Boris Burkov
2025-10-03 23:41 ` [PATCH v2 3/3] fstests: btrfs: test RAID conversions under stress Leo Martins
2025-10-04 1:54 ` Qu Wenruo
2025-10-06 17:37 ` Leo Martins [this message]
2025-10-06 18:16 ` David Sterba
2025-10-15 3:31 ` Boris Burkov
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=20251006173757.296087-1-loemra.dev@gmail.com \
--to=loemra.dev@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=kernel-team@fb.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.