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/5 v2] Struct to fs_info helpers
Date: Thu,  1 Feb 2024 19:02:20 +0100	[thread overview]
Message-ID: <cover.1706810422.git.dsterba@suse.com> (raw)

v2:

- move helper definitions to fs.h
- add _Generic to the macros for type checking
- reuse helpers to some code duplication

Add convenience helpers for getting a fs_info from page, bio, inode etc.
There's one prep patch where tests use a normal helper that expects
valid inode->root->fs_info.

David Sterba (5):
  btrfs: tests: allocate dummy fs_info and root in test_find_delalloc()
  btrfs: add helpers to get inode from page/folio pointers
  btrfs: add helpers to get fs_info from page/folio pointers
  btrfs: add helper to get fs_info from struct inode pointer
  btrfs: hoist fs_info out of loops in end_bbio_data_write and
    end_bbio_data_read

 fs/btrfs/compression.c           |  8 +++---
 fs/btrfs/defrag.c                |  4 +--
 fs/btrfs/disk-io.c               | 11 ++++----
 fs/btrfs/export.c                |  2 +-
 fs/btrfs/extent_io.c             | 45 ++++++++++++++++----------------
 fs/btrfs/file.c                  | 14 +++++-----
 fs/btrfs/free-space-cache.c      |  2 +-
 fs/btrfs/fs.h                    | 11 ++++++++
 fs/btrfs/inode.c                 | 42 ++++++++++++++---------------
 fs/btrfs/ioctl.c                 | 40 ++++++++++++++--------------
 fs/btrfs/lzo.c                   |  4 +--
 fs/btrfs/props.c                 |  2 +-
 fs/btrfs/reflink.c               |  6 ++---
 fs/btrfs/relocation.c            |  2 +-
 fs/btrfs/tests/extent-io-tests.c | 28 +++++++++++++++++---
 15 files changed, 126 insertions(+), 95 deletions(-)

-- 
2.42.1


             reply	other threads:[~2024-02-01 18:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 18:02 David Sterba [this message]
2024-02-01 18:02 ` [PATCH 1/5] btrfs: tests: allocate dummy fs_info and root in test_find_delalloc() David Sterba
2024-02-01 18:02 ` [PATCH 2/5] btrfs: add helpers to get inode from page/folio pointers David Sterba
2024-02-01 18:02 ` [PATCH 3/5] btrfs: add helpers to get fs_info " David Sterba
2024-02-01 18:02 ` [PATCH 4/5] btrfs: add helper to get fs_info from struct inode pointer David Sterba
2024-02-02 11:34   ` Johannes Thumshirn
2024-02-02 12:07     ` David Sterba
2024-02-02 12:09       ` Johannes Thumshirn
2024-02-01 18:02 ` [PATCH 5/5] btrfs: hoist fs_info out of loops in end_bbio_data_write and end_bbio_data_read David Sterba
2024-02-02 12:10 ` [PATCH 0/5 v2] Struct to fs_info helpers Johannes Thumshirn
2024-02-02 12:45 ` Anand Jain

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.1706810422.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