linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Kevin Brandstatter <icarusthecow@gmail.com>,
	<linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: Remove unused parameter "name" from btrfs_qgroup_create
Date: Thu, 10 Jul 2014 10:47:25 +0900	[thread overview]
Message-ID: <53BDF0AD.7030006@jp.fujitsu.com> (raw)
In-Reply-To: <53B76E71.3010709@gmail.com>

(2014/07/05 12:18), Kevin Brandstatter wrote:
> in btrfs_qgruop_create a fourth parameter "name" exists.
> however this parameter is not used anywhere in the function
> the only other place this function is called is ioctl and the call
> passes NULL as the name paremeter which would seem to indicate its
> lack of necessity.
>
> Signed-off-by: Kevin Brandstatter <kjbrandstatter@gmail.com>

Reviewed-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>

> ---
>   fs/btrfs/ioctl.c  | 3 +--
>   fs/btrfs/qgroup.c | 2 +-
>   fs/btrfs/qgroup.h | 3 +--
>   3 files changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index 2a99f49..4b33d08 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -4709,8 +4709,7 @@ static long btrfs_ioctl_qgroup_create(struct file
> *file, void __user *arg)
>
>       /* FIXME: check if the IDs really exist */
>       if (sa->create) {
> -        ret = btrfs_create_qgroup(trans, root->fs_info, sa->qgroupid,
> -                      NULL);
> +        ret = btrfs_create_qgroup(trans, root->fs_info, sa->qgroupid);
>       } else {
>           ret = btrfs_remove_qgroup(trans, root->fs_info, sa->qgroupid);
>       }
> diff --git a/fs/btrfs/qgroup.c b/fs/btrfs/qgroup.c
> index 98cb6b2..3d1c8be 100644
> --- a/fs/btrfs/qgroup.c
> +++ b/fs/btrfs/qgroup.c
> @@ -1091,7 +1091,7 @@ out:
>   }
>
>   int btrfs_create_qgroup(struct btrfs_trans_handle *trans,
> -            struct btrfs_fs_info *fs_info, u64 qgroupid, char *name)
> +            struct btrfs_fs_info *fs_info, u64 qgroupid)
>   {
>       struct btrfs_root *quota_root;
>       struct btrfs_qgroup *qgroup;
> diff --git a/fs/btrfs/qgroup.h b/fs/btrfs/qgroup.h
> index 5952ff1..31403ca 100644
> --- a/fs/btrfs/qgroup.h
> +++ b/fs/btrfs/qgroup.h
> @@ -69,8 +69,7 @@ int btrfs_add_qgroup_relation(struct
> btrfs_trans_handle *trans,
>   int btrfs_del_qgroup_relation(struct btrfs_trans_handle *trans,
>                     struct btrfs_fs_info *fs_info, u64 src, u64 dst);
>   int btrfs_create_qgroup(struct btrfs_trans_handle *trans,
> -            struct btrfs_fs_info *fs_info, u64 qgroupid,
> -            char *name);
> +            struct btrfs_fs_info *fs_info, u64 qgroupid);
>   int btrfs_remove_qgroup(struct btrfs_trans_handle *trans,
>                     struct btrfs_fs_info *fs_info, u64 qgroupid);
>   int btrfs_limit_qgroup(struct btrfs_trans_handle *trans,
>


      reply	other threads:[~2014-07-10  1:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-05  3:18 [PATCH] btrfs: Remove unused parameter "name" from btrfs_qgroup_create Kevin Brandstatter
2014-07-10  1:47 ` Satoru Takeuchi [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=53BDF0AD.7030006@jp.fujitsu.com \
    --to=takeuchi_satoru@jp.fujitsu.com \
    --cc=icarusthecow@gmail.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).