public inbox for linux-btrfs@vger.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 00/12] btrfs: various cleanups to make ctree.c sync easier
Date: Sat, 29 Apr 2023 16:07:09 -0400	[thread overview]
Message-ID: <cover.1682798736.git.josef@toxicpanda.com> (raw)

Hello,

These are various cleanups I needed to make syncing some of the kernel files
into btrfs-progs go smoothly.  They're cosmetic and organizational and shouldn't
have any functional changes.  Thanks,

Josef

Josef Bacik (12):
  btrfs: move btrfs_check_trunc_cache_free_space into block-rsv.c
  btrfs: remove level argument from btrfs_set_block_flags
  btrfs: simplify btrfs_check_leaf_* helpers into a single helper
  btrfs: add btrfs_tree_block_status definitions to tree-checker.h
  btrfs: use btrfs_tree_block_status for leaf item errors
  btrfs: extend btrfs_leaf_check to return btrfs_tree_block_status
  btrfs: add __btrfs_check_node helper
  btrfs: move btrfs_verify_level_key into tree-checker.c
  btrfs: move split_flags/combine_flags helpers to inode-item.h
  btrfs: add __KERNEL__ check for btrfs_no_printk
  btrfs: add a btrfs_csum_type_size helper
  btrfs: rename del_ptr -> btrfs_del_ptr and export it

 fs/btrfs/block-rsv.c        |  19 +++++
 fs/btrfs/block-rsv.h        |   2 +
 fs/btrfs/btrfs_inode.h      |  16 ----
 fs/btrfs/ctree.c            |  29 ++++---
 fs/btrfs/ctree.h            |   3 +
 fs/btrfs/disk-io.c          |  70 ++--------------
 fs/btrfs/disk-io.h          |   2 -
 fs/btrfs/extent-tree.c      |   7 +-
 fs/btrfs/extent-tree.h      |   2 +-
 fs/btrfs/free-space-cache.c |  19 -----
 fs/btrfs/free-space-cache.h |   2 -
 fs/btrfs/inode-item.h       |  16 ++++
 fs/btrfs/messages.h         |   7 ++
 fs/btrfs/tree-checker.c     | 157 ++++++++++++++++++++++++++----------
 fs/btrfs/tree-checker.h     |  29 ++++---
 15 files changed, 207 insertions(+), 173 deletions(-)

-- 
2.40.0


             reply	other threads:[~2023-04-29 20:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-29 20:07 Josef Bacik [this message]
2023-04-29 20:07 ` [PATCH 01/12] btrfs: move btrfs_check_trunc_cache_free_space into block-rsv.c Josef Bacik
2023-05-02 11:16   ` Johannes Thumshirn
2023-04-29 20:07 ` [PATCH 02/12] btrfs: remove level argument from btrfs_set_block_flags Josef Bacik
2023-05-02 11:17   ` Johannes Thumshirn
2023-04-29 20:07 ` [PATCH 03/12] btrfs: simplify btrfs_check_leaf_* helpers into a single helper Josef Bacik
2023-05-02 11:27   ` Johannes Thumshirn
2023-05-09 21:01     ` David Sterba
2023-04-29 20:07 ` [PATCH 04/12] btrfs: add btrfs_tree_block_status definitions to tree-checker.h Josef Bacik
2023-05-02 11:32   ` Johannes Thumshirn
2023-04-29 20:07 ` [PATCH 05/12] btrfs: use btrfs_tree_block_status for leaf item errors Josef Bacik
2023-05-02 11:48   ` Johannes Thumshirn
2023-04-29 20:07 ` [PATCH 06/12] btrfs: extend btrfs_leaf_check to return btrfs_tree_block_status Josef Bacik
2023-05-02 12:03   ` Johannes Thumshirn
2023-05-09 21:01     ` David Sterba
2023-04-29 20:07 ` [PATCH 07/12] btrfs: add __btrfs_check_node helper Josef Bacik
2023-05-02 12:10   ` Johannes Thumshirn
2023-05-09 22:07     ` David Sterba
2023-04-29 20:07 ` [PATCH 08/12] btrfs: move btrfs_verify_level_key into tree-checker.c Josef Bacik
2023-05-02 12:25   ` Johannes Thumshirn
2023-04-29 20:07 ` [PATCH 09/12] btrfs: move split_flags/combine_flags helpers to inode-item.h Josef Bacik
2023-05-02 12:27   ` Johannes Thumshirn
2023-04-29 20:07 ` [PATCH 10/12] btrfs: add __KERNEL__ check for btrfs_no_printk Josef Bacik
2023-05-02 12:28   ` Johannes Thumshirn
2023-04-29 20:07 ` [PATCH 11/12] btrfs: add a btrfs_csum_type_size helper Josef Bacik
2023-05-02 12:34   ` Johannes Thumshirn
2023-04-29 20:07 ` [PATCH 12/12] btrfs: rename del_ptr -> btrfs_del_ptr and export it Josef Bacik
2023-05-02 12:35   ` Johannes Thumshirn
2023-05-09 22:10 ` [PATCH 00/12] btrfs: various cleanups to make ctree.c sync easier 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.1682798736.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox