public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/9] btrfs: some header cleanups and move things around
Date: Mon, 16 Dec 2024 17:17:15 +0000	[thread overview]
Message-ID: <cover.1734368270.git.fdmanana@suse.com> (raw)

From: Filipe Manana <fdmanana@suse.com>

Move some misplaced prototypes, macros and functions around and some
header cleanups. Trivial changes, details in the change logs.

Filipe Manana (9):
  btrfs: move abort_should_print_stack() to transaction.h
  btrfs: move csum related functions from ctree.c into fs.c
  btrfs: move the exclusive operation functions into fs.c
  btrfs: move btrfs_is_empty_uuid() from ioctl.c into fs.c
  btrfs: move the folio ordered helpers from ctree.h into fs.h
  btrfs: move BTRFS_BYTES_TO_BLKS() into fs.h
  btrfs: move btrfs_alloc_write_mask() into fs.h
  btrfs: move extent-tree function declarations out of ctree.h
  btrfs: remove pointless comment from ctree.h

 fs/btrfs/ctree.c            |  67 -----------------
 fs/btrfs/ctree.h            |  29 --------
 fs/btrfs/extent-tree.h      |   4 ++
 fs/btrfs/free-space-cache.c |   2 +-
 fs/btrfs/fs.c               | 139 ++++++++++++++++++++++++++++++++++++
 fs/btrfs/fs.h               |  24 +++++++
 fs/btrfs/ioctl.c            |  91 -----------------------
 fs/btrfs/ioctl.h            |   1 -
 fs/btrfs/transaction.h      |  18 ++++-
 fs/btrfs/volumes.c          |   2 +-
 10 files changed, 185 insertions(+), 192 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-12-16 17:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 17:17 fdmanana [this message]
2024-12-16 17:17 ` [PATCH 1/9] btrfs: move abort_should_print_stack() to transaction.h fdmanana
2024-12-16 17:17 ` [PATCH 2/9] btrfs: move csum related functions from ctree.c into fs.c fdmanana
2024-12-17  0:26   ` Qu Wenruo
2024-12-17  8:55     ` Filipe Manana
2024-12-18 20:14       ` David Sterba
2024-12-18 20:21   ` David Sterba
2024-12-18 20:45     ` Filipe Manana
2024-12-18 21:28       ` Qu Wenruo
2024-12-23 19:36         ` David Sterba
2024-12-23 19:26       ` David Sterba
2024-12-16 17:17 ` [PATCH 3/9] btrfs: move the exclusive operation functions " fdmanana
2024-12-16 17:17 ` [PATCH 4/9] btrfs: move btrfs_is_empty_uuid() from ioctl.c " fdmanana
2024-12-17  0:31   ` Qu Wenruo
2024-12-17  7:53     ` Johannes Thumshirn
2024-12-17  8:06       ` Qu Wenruo
2024-12-17  8:57     ` Filipe Manana
2024-12-17  9:03       ` Qu Wenruo
2024-12-16 17:17 ` [PATCH 5/9] btrfs: move the folio ordered helpers from ctree.h into fs.h fdmanana
2024-12-16 17:17 ` [PATCH 6/9] btrfs: move BTRFS_BYTES_TO_BLKS() " fdmanana
2024-12-16 17:17 ` [PATCH 7/9] btrfs: move btrfs_alloc_write_mask() " fdmanana
2024-12-16 17:17 ` [PATCH 8/9] btrfs: move extent-tree function declarations out of ctree.h fdmanana
2024-12-16 17:17 ` [PATCH 9/9] btrfs: remove pointless comment from ctree.h fdmanana
2024-12-17  4:08 ` [PATCH 0/9] btrfs: some header cleanups and move things around Qu Wenruo
2024-12-17 11:57 ` Johannes Thumshirn
2024-12-18 20:23 ` 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.1734368270.git.fdmanana@suse.com \
    --to=fdmanana@kernel.org \
    --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