All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/4] btrfs: some extent tree modification cleanups
Date: Wed, 23 Feb 2022 14:06:42 -0500	[thread overview]
Message-ID: <cover.1645643109.git.josef@toxicpanda.com> (raw)

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

 fs/btrfs/extent-tree.c | 141 +++++++++++++++++++----------------------
 1 file changed, 66 insertions(+), 75 deletions(-)

-- 
2.26.3


             reply	other threads:[~2022-02-23 19:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 19:06 Josef Bacik [this message]
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 ` [PATCH 0/4] btrfs: some extent tree modification cleanups 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=cover.1645643109.git.josef@toxicpanda.com \
    --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 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.