public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com
Subject: [PATCH 0/2] btrfs: send: two tiny unused parameter cleanups
Date: Thu,  4 Nov 2021 17:00:11 -0700	[thread overview]
Message-ID: <cover.1636070238.git.osandov@fb.com> (raw)

From: Omar Sandoval <osandov@fb.com>

I encountered some places where we pass around btrfs_dir_type()
unnecessarily while I was working on fscrypt support. I might need to
stuff a flag in btrfs_dir_type() for fscrypt, so using dir_type in less
places makes it easier to audit that change. Either way, these are
unused parameters so we should just drop them as a cleanup.

Omar Sandoval (2):
  btrfs: send: remove unused found_type parameter to
    lookup_dir_item_inode()
  btrfs: send: remove unused type parameter to iterate_inode_ref_t

 fs/btrfs/send.c | 43 +++++++++++++++++--------------------------
 1 file changed, 17 insertions(+), 26 deletions(-)

-- 
2.33.1


             reply	other threads:[~2021-11-05  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05  0:00 Omar Sandoval [this message]
2021-11-05  0:00 ` [PATCH 1/2] btrfs: send: remove unused found_type parameter to lookup_dir_item_inode() Omar Sandoval
2021-11-05  0:00 ` [PATCH 2/2] btrfs: send: remove unused type parameter to iterate_inode_ref_t Omar Sandoval
2021-11-05 10:07 ` [PATCH 0/2] btrfs: send: two tiny unused parameter cleanups Josef Bacik
2021-11-05 10:13 ` Nikolay Borisov
2021-11-08 19:40 ` 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.1636070238.git.osandov@fb.com \
    --to=osandov@osandov.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox