public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Burkov <boris@bur.io>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] Parameter cleanups for subvolume/snapshots ioctls
Date: Mon, 30 Jun 2025 16:45:41 -0700	[thread overview]
Message-ID: <20250630234541.GA1265689@zen.localdomain> (raw)
In-Reply-To: <cover.1750948128.git.dsterba@suse.com>

On Thu, Jun 26, 2025 at 04:30:08PM +0200, David Sterba wrote:
> Use qstr for name + length parameters, some other parameter type or name
> adjustments.

Reviewed-by: Boris Burkov <boris@bur.io>

> 
> David Sterba (4):
>   btrfs: use struct qstr for subvolume ioctl helpers
>   btrfs: pass dentry to btrfs_mksubvol() and btrfs_mksnapshot()
>   btrfs: pass bool to indicate subvolume/snapshot creation type
>   btrfs: rename inode number parameter passed to
>     btrfs_check_dir_item_collision()
> 
>  fs/btrfs/dir-item.c |  4 ++--
>  fs/btrfs/dir-item.h |  2 +-
>  fs/btrfs/ioctl.c    | 37 +++++++++++++++++--------------------
>  3 files changed, 20 insertions(+), 23 deletions(-)
> 
> -- 
> 2.49.0
> 

      parent reply	other threads:[~2025-06-30 23:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26 14:30 [PATCH 0/4] Parameter cleanups for subvolume/snapshots ioctls David Sterba
2025-06-26 14:30 ` [PATCH 1/4] btrfs: use struct qstr for subvolume ioctl helpers David Sterba
2025-06-26 14:30 ` [PATCH 2/4] btrfs: pass dentry to btrfs_mksubvol() and btrfs_mksnapshot() David Sterba
2025-06-26 14:30 ` [PATCH 3/4] btrfs: pass bool to indicate subvolume/snapshot creation type David Sterba
2025-06-26 14:30 ` [PATCH 4/4] btrfs: rename inode number parameter passed to btrfs_check_dir_item_collision() David Sterba
2025-06-30 23:45 ` Boris Burkov [this message]

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=20250630234541.GA1265689@zen.localdomain \
    --to=boris@bur.io \
    --cc=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