From: David Sterba <dsterba@suse.cz>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Qu Wenru <wqu@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH 0/4] btrfs: RAID stripe tree updates
Date: Mon, 18 Sep 2023 18:39:36 +0200 [thread overview]
Message-ID: <20230918163936.GJ2747@suse.cz> (raw)
In-Reply-To: <20230918-rst-updates-v1-0-17686dc06859@wdc.com>
On Mon, Sep 18, 2023 at 07:14:29AM -0700, Johannes Thumshirn wrote:
> Here is a first batch of updates for the RAID stripe tree patchset in
> for-next which address some of the review comments.
Thanks.
> ---
> Johannes Thumshirn (4):
> btrfs: fix 64bit division in btrfs_insert_striped_mirrored_raid_extents
> btrfs: break loop in case set_io_stripe fails
> btrfs: rename ordered_enmtry in btrfs_io_context
Folded to the patches.
> btrfs: add tree-checker for RAID-stripe-tree
Added as a new one.
prev parent reply other threads:[~2023-09-18 16:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 14:14 [PATCH 0/4] btrfs: RAID stripe tree updates Johannes Thumshirn
2023-09-18 14:14 ` [PATCH 1/4] btrfs: fix 64bit division in btrfs_insert_striped_mirrored_raid_extents Johannes Thumshirn
2023-09-18 14:18 ` Geert Uytterhoeven
2023-09-18 15:03 ` Johannes Thumshirn
2023-09-18 16:24 ` David Sterba
2023-09-18 18:31 ` Geert Uytterhoeven
2023-09-18 21:07 ` David Sterba
2023-09-19 0:37 ` Qu Wenruo
2023-09-19 13:58 ` David Sterba
2023-09-19 21:50 ` Qu Wenruo
2023-09-20 15:34 ` David Sterba
2023-09-18 14:14 ` [PATCH 2/4] btrfs: break loop in case set_io_stripe fails Johannes Thumshirn
2023-09-18 14:14 ` [PATCH 3/4] btrfs: rename ordered_enmtry in btrfs_io_context Johannes Thumshirn
2023-09-18 14:14 ` [PATCH 4/4] btrfs: add tree-checker for RAID-stripe-tree Johannes Thumshirn
2023-09-19 0:30 ` Qu Wenruo
2023-09-18 16:39 ` David Sterba [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=20230918163936.GJ2747@suse.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=geert@linux-m68k.org \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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 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 NNTP newsgroup(s).