From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz
Cc: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 00/12] btrfs: scrub: use a more reader friendly code to implement scrub_simple_mirror()
Date: Fri, 24 Mar 2023 08:42:22 +0800 [thread overview]
Message-ID: <10dba572-0877-b372-3790-32bd6c116afa@gmx.com> (raw)
In-Reply-To: <20230323175118.GV10580@twin.jikos.cz>
On 2023/3/24 01:51, David Sterba wrote:
> On Thu, Mar 23, 2023 at 02:28:16PM +0800, Qu Wenruo wrote:
>>
>>
>> On 2023/3/21 08:09, David Sterba wrote:
>>> On Mon, Mar 20, 2023 at 10:12:46AM +0800, Qu Wenruo wrote:
>>>> [TODO]
>>>>
>>>> - More testing on zoned devices
>>>> Now the patchset can already pass all scrub/replace groups with
>>>> regular devices.
>>>
>>> I think I noticed some disparity in the old and new code for the zoned
>>> devices. This should be found by testing so I'd add this series to
>>> for-next and see.
>>
>> Just want to be sure, if I want to further update the series (mostly
>> style and small cleanups), I should just base all my updates on your
>> for-next branch, right?
>
> No, please base it on misc-next. For-next is for an early testing but
> patchsets can be updated or completely dropped.
My bad, my question should be: Should I fetch all the patches from for-next?
Because I thought there may be some modification when you apply the
patches, but it turns out it's really applied as is, so no need for that.
All my patches are and will always be based on misc-next.
(Although sometimes it's some older misc-next)
Thanks,
Qu
next prev parent reply other threads:[~2023-03-24 0:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 2:12 [PATCH v3 00/12] btrfs: scrub: use a more reader friendly code to implement scrub_simple_mirror() Qu Wenruo
2023-03-20 2:12 ` [PATCH v3 01/12] btrfs: scrub: use dedicated super block verification function to scrub one super block Qu Wenruo
2023-03-21 5:22 ` Anand Jain
2023-03-21 7:25 ` Qu Wenruo
2023-03-21 22:12 ` David Sterba
2023-03-20 2:12 ` [PATCH v3 02/12] btrfs: introduce a new helper to submit bio for scrub Qu Wenruo
2023-03-21 12:02 ` Christoph Hellwig
2023-03-24 9:58 ` Qu Wenruo
2023-03-25 8:09 ` Christoph Hellwig
2023-03-25 8:21 ` Qu Wenruo
2023-03-25 8:31 ` Christoph Hellwig
2023-03-25 8:48 ` Qu Wenruo
2023-03-27 3:36 ` Christoph Hellwig
2023-03-20 2:12 ` [PATCH v3 03/12] btrfs: introduce a new helper to submit write " Qu Wenruo
2023-03-21 0:14 ` David Sterba
2023-03-21 0:54 ` Qu Wenruo
2023-03-21 1:27 ` David Sterba
2023-03-23 8:48 ` Qu Wenruo
2023-03-20 2:12 ` [PATCH v3 04/12] btrfs: scrub: introduce the structure for new BTRFS_STRIPE_LEN based interface Qu Wenruo
2023-03-21 0:22 ` David Sterba
2023-03-20 2:12 ` [PATCH v3 05/12] btrfs: scrub: introduce a helper to find and fill the sector info for a scrub_stripe Qu Wenruo
2023-03-20 2:12 ` [PATCH v3 06/12] btrfs: scrub: introduce a helper to verify one metadata Qu Wenruo
2023-03-21 0:31 ` David Sterba
2023-03-20 2:12 ` [PATCH v3 07/12] btrfs: scrub: introduce a helper to verify one scrub_stripe Qu Wenruo
2023-03-20 2:12 ` [PATCH v3 08/12] btrfs: scrub: introduce the main read repair worker for scrub_stripe Qu Wenruo
2023-03-20 2:12 ` [PATCH v3 09/12] btrfs: scrub: introduce a writeback helper " Qu Wenruo
2023-03-21 0:43 ` David Sterba
2023-03-20 2:12 ` [PATCH v3 10/12] btrfs: scrub: introduce error reporting functionality " Qu Wenruo
2023-03-20 2:12 ` [PATCH v3 11/12] btrfs: scrub: introduce the helper to queue a stripe for scrub Qu Wenruo
2023-03-20 2:12 ` [PATCH v3 12/12] btrfs: scrub: switch scrub_simple_mirror() to scrub_stripe infrastructure Qu Wenruo
2023-03-21 1:12 ` David Sterba
2023-03-21 0:09 ` [PATCH v3 00/12] btrfs: scrub: use a more reader friendly code to implement scrub_simple_mirror() David Sterba
2023-03-23 6:28 ` Qu Wenruo
2023-03-23 17:51 ` David Sterba
2023-03-24 0:42 ` Qu Wenruo [this message]
2023-03-27 23:28 ` 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=10dba572-0877-b372-3790-32bd6c116afa@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--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.