All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Martins <loemra.dev@gmail.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH v3 0/2] clean up iget_path, read_locked_inode
Date: Wed, 21 Aug 2024 14:31:01 -0700	[thread overview]
Message-ID: <cover.1724267937.git.loemra.dev@gmail.com> (raw)

The first patch moves the path allocation from
btrfs_read_locked_inode to btrfs_iget_path. It makes
more sense to handle a path allocation outside of 
read_locked_inode.

The second patch moves the clean up code from
btrfs_iget_path into btrfs_read_locked_inode 
simplifying btrfs_iget_path.

Leo Martins (2):
  btrfs: move path allocation to btrfs_iget_path
  btrfs: move cleanup code to read_locked_inode

 fs/btrfs/inode.c | 125 +++++++++++++++++++++++------------------------
 1 file changed, 62 insertions(+), 63 deletions(-)

-- 
2.43.5


             reply	other threads:[~2024-08-21 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21 21:31 Leo Martins [this message]
2024-08-21 21:31 ` [PATCH v3 1/2] btrfs: move path allocation to btrfs_iget_path Leo Martins
2024-08-21 21:31 ` [PATCH v3 2/2] btrfs: move cleanup code to read_locked_inode Leo Martins

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.1724267937.git.loemra.dev@gmail.com \
    --to=loemra.dev@gmail.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.