public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/7] Cleanups for 6.15
Date: Wed, 12 Feb 2025 21:21:41 +0100	[thread overview]
Message-ID: <cover.1739391605.git.dsterba@suse.com> (raw)

David Sterba (7):
  btrfs: add __cold attribute to extent_io_tree_panic()
  btrfs: async-thread: switch local variables need_order bool
  btrfs: zstd: move zstd_parameters to the workspace
  btrfs: zstd: remove local variable for storing page offsets
  btrfs: unify ordering of btrfs_key initializations
  btrfs: simplify returns and labels in btrfs_init_fs_root()
  btrfs: update include and forward declarations in headers

 fs/btrfs/accessors.h        |  1 +
 fs/btrfs/acl.h              |  2 ++
 fs/btrfs/async-thread.c     | 11 +++++------
 fs/btrfs/backref.c          |  4 ++--
 fs/btrfs/block-group.c      |  6 +++---
 fs/btrfs/ctree.h            |  2 +-
 fs/btrfs/delayed-ref.h      |  2 ++
 fs/btrfs/dir-item.h         |  1 +
 fs/btrfs/direct-io.h        |  2 ++
 fs/btrfs/discard.h          |  1 +
 fs/btrfs/disk-io.c          | 11 +++++------
 fs/btrfs/export.c           |  2 +-
 fs/btrfs/extent-io-tree.c   |  8 ++++----
 fs/btrfs/extent-tree.c      |  8 ++++----
 fs/btrfs/extent-tree.h      |  1 -
 fs/btrfs/file-item.c        | 13 +++++++------
 fs/btrfs/file-item.h        |  2 ++
 fs/btrfs/file.h             |  2 ++
 fs/btrfs/free-space-cache.c |  8 ++++----
 fs/btrfs/fs.c               |  1 -
 fs/btrfs/inode-item.c       |  6 +++---
 fs/btrfs/inode.c            |  8 ++++----
 fs/btrfs/ioctl.c            |  4 ++--
 fs/btrfs/ioctl.h            |  2 ++
 fs/btrfs/locking.c          |  1 -
 fs/btrfs/ordered-data.h     |  1 +
 fs/btrfs/print-tree.h       |  2 ++
 fs/btrfs/props.h            |  1 +
 fs/btrfs/qgroup.c           |  2 +-
 fs/btrfs/qgroup.h           |  3 +++
 fs/btrfs/raid-stripe-tree.h |  1 +
 fs/btrfs/scrub.c            |  4 ++--
 fs/btrfs/send.c             |  1 -
 fs/btrfs/space-info.c       |  2 +-
 fs/btrfs/subpage.c          |  1 -
 fs/btrfs/sysfs.h            |  1 +
 fs/btrfs/transaction.c      |  2 +-
 fs/btrfs/tree-log.c         |  6 +++---
 fs/btrfs/volumes.c          | 16 ++++++++--------
 fs/btrfs/volumes.h          |  4 ++++
 fs/btrfs/xattr.h            |  2 ++
 fs/btrfs/zstd.c             | 14 ++++++--------
 42 files changed, 97 insertions(+), 75 deletions(-)

-- 
2.47.1


             reply	other threads:[~2025-02-12 20:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12 20:21 David Sterba [this message]
2025-02-12 20:21 ` [PATCH 1/7] btrfs: add __cold attribute to extent_io_tree_panic() David Sterba
2025-02-12 20:22 ` [PATCH 2/7] btrfs: async-thread: switch local variables need_order bool David Sterba
2025-02-12 20:22 ` [PATCH 3/7] btrfs: zstd: move zstd_parameters to the workspace David Sterba
2025-02-12 20:22 ` [PATCH 4/7] btrfs: zstd: remove local variable for storing page offsets David Sterba
2025-02-12 20:22 ` [PATCH 5/7] btrfs: unify ordering of btrfs_key initializations David Sterba
2025-02-12 20:22 ` [PATCH 6/7] btrfs: simplify returns and labels in btrfs_init_fs_root() David Sterba
2025-02-12 20:22 ` [PATCH 7/7] btrfs: update include and forward declarations in headers 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.1739391605.git.dsterba@suse.com \
    --to=dsterba@suse.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