mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Mark Korenberg <socketpair@gmail.com>
Cc: David Sterba <dsterba@suse.com>, Chris Mason <mason@kernel.org>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] btrfs: raid56: pass REQ_META to per-device bios
Date: Tue, 10 Nov 2026 18:27:22 +1030	[thread overview]
Message-ID: <193ce29f-86f0-41f2-9c32-a2e0f8f4aba1@suse.com> (raw)
In-Reply-To: <f05b71b2a735d2b9d018c072f30a0b78@gmail.com>



在 2026/11/10 18:05, Mark Korenberg 写道:
> On 2026/11/7 06:56, Qu Wenruo wrote:
>> NACK.
>>
>> One should not even use RAID56 for metadata chunks in the first place.
>> Nor we're any different from other RAID56 implementation.
> 
> Fair enough, I'm dropping this patch.  Thanks for the reviews.
> 
> David, patch 1/2 stands on its own and has Qu's Reviewed-by.  Could
> you take it from this series, or would you prefer a v3 with only that
> patch?

No need to resent. A reviewed-by from any of the known developers is 
enough to get it merged.

The first patch is already pushed to for-next branch.

Thanks,
Qu

      reply	other threads:[~2026-11-10  7:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 17:33 [PATCH v2 0/2] btrfs: tag tree block repair and RAID5/6 metadata I/O with REQ_META Mark Korenberg via B4 Relay
2026-11-06 17:33 ` [PATCH v2 1/2] btrfs: tag tree block repair writes " Mark Korenberg via B4 Relay
2026-11-06 20:31   ` Qu Wenruo
2026-11-06 17:33 ` [PATCH v2 2/2] btrfs: raid56: pass REQ_META to per-device bios Mark Korenberg via B4 Relay
2026-11-06 20:26   ` Qu Wenruo
2026-11-10  7:35     ` Mark Korenberg
2026-11-10  7:57       ` Qu Wenruo [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=193ce29f-86f0-41f2-9c32-a2e0f8f4aba1@suse.com \
    --to=wqu@suse.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@kernel.org \
    --cc=socketpair@gmail.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
all inboxes | Powered by JetHome®