linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sahil Kang <sahil.kang@asilaycomputing.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/1] btrfs: reuse existing pointers from btrfs_ioctl
Date: Wed,  5 Jan 2022 00:30:05 -0800	[thread overview]
Message-ID: <20220105083006.2793559-1-sahil.kang@asilaycomputing.com> (raw)

This is a small cleanup that reuses some of the existing pointers and
removes the duplicated dereferencing.

There are other subfunctions that have similar/identical dereferencing
as the enclosing btrfs_ioctl, but I'm not sure if changing those is
welcomed since it would require changing their arg count. Right now,
all of the sub ioctl functions have essentially the same signature.

For example, reusing the pointers for btrfs_ioctl_set_fslabel would
require passing in *fs_info and *root, in addition to its current
args.

Sahil Kang (1):
  btrfs: reuse existing pointers from btrfs_ioctl

 fs/btrfs/ioctl.c | 28 +++++++++++-----------------
 1 file changed, 11 insertions(+), 17 deletions(-)

-- 
Sahil


             reply	other threads:[~2022-01-05  8:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05  8:30 Sahil Kang [this message]
2022-01-05  8:30 ` [PATCH 1/1] btrfs: reuse existing pointers from btrfs_ioctl Sahil Kang
2022-01-05  9:53   ` Qu Wenruo
2022-01-06 15:03     ` David Sterba
2022-01-16  2:48       ` [PATCH 0/1] btrfs: reuse existing inode " Sahil Kang
2022-01-16  2:48         ` [PATCH 1/1] " Sahil Kang
2022-01-17 13:39           ` David Sterba
2022-01-06 15:27   ` [PATCH 1/1] btrfs: reuse existing pointers " David Sterba
2022-01-05  9:30 ` [PATCH 0/1] " Qu Wenruo
2022-01-06 15:11   ` 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=20220105083006.2793559-1-sahil.kang@asilaycomputing.com \
    --to=sahil.kang@asilaycomputing.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;
as well as URLs for NNTP newsgroup(s).