From: David Sterba <dsterba@suse.cz>
To: Johannes Thumshirn <jth@kernel.org>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Qu Wenru <wqu@suse.com>, Filipe Manana <fdmanana@suse.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: Re: [PATCH v3 2/3] btrfs: replace stripe extents
Date: Thu, 18 Jul 2024 17:35:10 +0200 [thread overview]
Message-ID: <20240718153510.GH8022@twin.jikos.cz> (raw)
In-Reply-To: <20240712-b4-rst-updates-v3-2-5cf27dac98a7@kernel.org>
On Fri, Jul 12, 2024 at 09:48:37AM +0200, Johannes Thumshirn wrote:
> From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
>
> Update stripe extents in case a write to an already existing address
> incoming.
>
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Please update the subject and changelog (in for-next), this does explain
much or lacks context. Thanks.
next prev parent reply other threads:[~2024-07-18 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 7:48 [PATCH v3 0/3] btrfs: more RAID stripe tree updates Johannes Thumshirn
2024-07-12 7:48 ` [PATCH v3 1/3] btrfs: don't hold dev_replace rwsem over whole of btrfs_map_block Johannes Thumshirn
2024-07-15 11:29 ` Filipe Manana
2024-07-15 11:38 ` Johannes Thumshirn
2024-07-12 7:48 ` [PATCH v3 2/3] btrfs: replace stripe extents Johannes Thumshirn
2024-07-12 10:19 ` Qu Wenruo
2024-07-18 15:35 ` David Sterba [this message]
2024-07-12 7:48 ` [PATCH v3 3/3] btrfs: update stripe_extent delete loop assumptions Johannes Thumshirn
2024-07-15 12:41 ` [PATCH v3 0/3] btrfs: more RAID stripe tree updates 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=20240718153510.GH8022@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=jth@kernel.org \
--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