All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kenneth Dsouza <kdsouza@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs4_getfacl: Add support to accept more paths
Date: Wed, 31 Jan 2018 15:16:05 -0500	[thread overview]
Message-ID: <20180131201605.GC3814@fieldses.org> (raw)
In-Reply-To: <CAA_-hQKaiEBUmKZj_o9fv-MOSvTgffACP8TrPPXGwk6x=MwkCA@mail.gmail.com>

On Wed, Jan 31, 2018 at 12:53:04AM +0530, Kenneth Dsouza wrote:
> Currently, nfs4_getfacl accepts only a single path at a time, which
> makes us run the command several times.
> This patch will help us to list (ACL) on multiple files at a  time.
>  nfs4getfacl file ...

Looks fine, thanks.

Just a couple whitespace nits:

> diff --git a/nfs4_getfacl/nfs4_getfacl.c b/nfs4_getfacl/nfs4_getfacl.c
> index 5363096..bbbbb62 100644
> --- a/nfs4_getfacl/nfs4_getfacl.c
> +++ b/nfs4_getfacl/nfs4_getfacl.c
> @@ -48,17 +48,13 @@ int main(int argc, char **argv)
>  {
>         struct nfs4_acl *acl;
>         int res = 1;
> -

No need to delete that blank line.

> +       int count = 1;
>         execname = basename(argv[0]);
> 
>         if (argc < 2) {
>                 fprintf(stderr, "%s: you must specify a path.\n", execname);
>                 usage(0);
>                 goto out;
> -       } else if (argc > 2) {
> -               fprintf(stderr, "%s: currently, you may only specify a
> single path.\n", execname);
> -               usage(0);
> -               goto out;
>         } else if (!strcmp(argv[1], "-?") || !strcmp(argv[1], "-h") ||
> !strcmp(argv[1], "--help")) {
>                 usage(1);
>                 res = 0;
> @@ -68,12 +64,15 @@ int main(int argc, char **argv)
>                 res = 0;
>                 goto out;
>         }
> -       acl = nfs4_acl_for_path(argv[1]);
> +       for (counter = 1; counter < agrc; counter++)    {
> +       acl = nfs4_acl_for_path(argv[counter]);
>         if (acl != NULL) {
> +               printf("\n# file: %s\n", argv[counter]);
>                 nfs4_print_acl(stdout, acl);
>                 nfs4_free_acl(acl);
>                 res = 0;
>         }

Fix the indentation here (the body of the loop should be indented.)

Actually the patch looks like the whitespace has been mangled somehow.
(For example the indentation is all tabs, not spaces, in the original.)

You might check
https://www.kernel.org/doc/html/v4.11/process/email-clients.html
and see if it has any hints for your email client.

--b.

> +       }
>  out:
>         return res;
>  }
> -- 
> 1.8.3.1

  reply	other threads:[~2018-01-31 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30 19:23 [PATCH] nfs4_getfacl: Add support to accept more paths Kenneth Dsouza
2018-01-31 20:16 ` J. Bruce Fields [this message]
2018-01-31 20:32   ` Kenneth Dsouza

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=20180131201605.GC3814@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=kdsouza@redhat.com \
    --cc=linux-nfs@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.