From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 0/4] btrfs: some extent tree modification cleanups
Date: Tue, 1 Mar 2022 17:26:22 +0100 [thread overview]
Message-ID: <20220301162622.GQ12643@twin.jikos.cz> (raw)
In-Reply-To: <cover.1645643109.git.josef@toxicpanda.com>
On Wed, Feb 23, 2022 at 02:06:42PM -0500, Josef Bacik wrote:
> Hello,
>
> These four patches are some prep/cleanup patches that I have for the next batch
> of extent tree v2 changes I have queued up. They are cosmetic, simply moving
> some code around and cleaning up some old cruft that was left over. Thanks,
>
> Josef
>
> Josef Bacik (4):
> btrfs: remove BUG_ON(ret) in alloc_reserved_tree_block
> btrfs: add a alloc_reserved_extent helper
> btrfs: remove `last_ref` from the extent freeing code
> btrfs: add a do_free_extent_accounting helper
Added to misc-next, thanks.
prev parent reply other threads:[~2022-03-01 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 19:06 [PATCH 0/4] btrfs: some extent tree modification cleanups Josef Bacik
2022-02-23 19:06 ` [PATCH 1/4] btrfs: remove BUG_ON(ret) in alloc_reserved_tree_block Josef Bacik
2022-02-23 19:06 ` [PATCH 2/4] btrfs: add a alloc_reserved_extent helper Josef Bacik
2022-02-23 19:06 ` [PATCH 3/4] btrfs: remove `last_ref` from the extent freeing code Josef Bacik
2022-02-23 19:06 ` [PATCH 4/4] btrfs: add a do_free_extent_accounting helper Josef Bacik
2022-03-01 16:26 ` 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=20220301162622.GQ12643@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=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