From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2 00/13] btrfs-progs: extent tree v2 global root support prep work
Date: Wed, 10 Nov 2021 15:11:41 -0500 [thread overview]
Message-ID: <YYwnfUhE1goNzJ7I@localhost.localdomain> (raw)
In-Reply-To: <cover.1636574767.git.josef@toxicpanda.com>
On Wed, Nov 10, 2021 at 03:07:51PM -0500, Josef Bacik wrote:
> v1->v2:
> - Added a "btrfs-progs: check: fix set_extent_dirty range" which I discovered
> when adding the next part of the changes.
> - Dropped all of the global root stuff, pushing it into the extent tree v2
> specific changes.
> - Reworked the super block root helper to take a level as suggested by Qu.
>
Sorry I'm an idiot, this should be v3, not v2, I forgot I had refreshed things
and sent out another v2 already. Thanks,
Josef
prev parent reply other threads:[~2021-11-10 20:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 20:07 [PATCH v2 00/13] btrfs-progs: extent tree v2 global root support prep work Josef Bacik
2021-11-10 20:07 ` [PATCH v2 01/13] btrfs-progs: check: fix set_extent_dirty range Josef Bacik
2021-11-10 20:07 ` [PATCH v2 02/13] btrfs-progs: simplify btrfs_make_block_group Josef Bacik
2021-11-10 20:07 ` [PATCH v2 03/13] btrfs-progs: check: don't walk down non fs-trees for qgroup check Josef Bacik
2021-11-10 20:07 ` [PATCH v2 04/13] btrfs-progs: filesystem-show: close ctree once we're done Josef Bacik
2021-11-10 20:07 ` [PATCH v2 05/13] btrfs-progs: add a helper for setting up a root node Josef Bacik
2021-11-10 20:07 ` [PATCH v2 06/13] btrfs-progs: btrfs-shared: stop passing root to csum related functions Josef Bacik
2021-11-15 18:54 ` David Sterba
2021-11-10 20:07 ` [PATCH v2 07/13] btrfs-progs: check: stop passing csum root around Josef Bacik
2021-11-10 20:07 ` [PATCH v2 08/13] btrfs-progs: stop accessing ->csum_root directly Josef Bacik
2021-11-10 20:08 ` [PATCH v2 09/13] btrfs-progs: image: keep track of seen blocks when walking trees Josef Bacik
2021-11-10 20:08 ` [PATCH v2 10/13] btrfs-progs: common: move btrfs_fix_block_accounting to repair.c Josef Bacik
2021-11-10 20:08 ` [PATCH v2 11/13] btrfs-progs: check: abstract out the used marking helpers Josef Bacik
2021-11-10 20:08 ` [PATCH v2 12/13] btrfs-progs: check: move btrfs_mark_used_tree_blocks to common Josef Bacik
2021-11-10 20:08 ` [PATCH v2 13/13] btrfs-progs: mark reloc roots as used Josef Bacik
2021-11-10 20:11 ` Josef Bacik [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=YYwnfUhE1goNzJ7I@localhost.localdomain \
--to=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
/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