All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
To: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>
Cc: Qu Wenru <wqu@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: [PATCH v2 0/2] btrfs: RAID stripe tree updates
Date: Wed, 20 Sep 2023 02:31:16 -0700	[thread overview]
Message-ID: <20230920-rst-updates-v2-0-b4dc154a648f@wdc.com> (raw)

Here is the second batch of updates for the RAID stripe tree patchset in
for-next which address some of the review comments.

---
- Link to first batch: https://lore.kernel.org/r/20230918-rst-updates-v1-0-17686dc06859@wdc.com

---
Johannes Thumshirn (2):
      btrfs: check for incompat bit in btrfs_insert_raid_extent
      btrfs: check for incompat bit in btrfs_need_stripe_tree_update

 fs/btrfs/raid-stripe-tree.c | 2 +-
 fs/btrfs/raid-stripe-tree.h | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
---
base-commit: e70275b918d304c9687a91e990a8ef440658c3bf
change-id: 20230915-rst-updates-8c55784ca4ef

Best regards,
-- 
Johannes Thumshirn <johannes.thumshirn@wdc.com>


             reply	other threads:[~2023-09-20  9:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20  9:31 Johannes Thumshirn [this message]
2023-09-20  9:31 ` [PATCH v2 1/2] btrfs: check for incompat bit in btrfs_insert_raid_extent Johannes Thumshirn
2023-09-20  9:31 ` [PATCH v2 2/2] btrfs: check for incompat bit in btrfs_need_stripe_tree_update Johannes Thumshirn
2023-09-20 14:50 ` [PATCH v2 0/2] btrfs: 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=20230920-rst-updates-v2-0-b4dc154a648f@wdc.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.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 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.