linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kinglong Mee <kinglongmee@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFSD: Cleanup unused comments and codes in summarize_posix_acl
Date: Thu, 8 May 2014 12:55:53 -0400	[thread overview]
Message-ID: <20140508165553.GF20976@fieldses.org> (raw)
In-Reply-To: <534A8D29.5070101@gmail.com>

I'd rather leave the comment there as long as we keep the memset.

I think you're right about the pe initialization, I don't know why
that's there....

--b.

On Sun, Apr 13, 2014 at 09:12:09PM +0800, Kinglong Mee wrote:
> Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
> ---
>  fs/nfsd/nfs4acl.c | 7 -------
>  1 file changed, 7 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4acl.c b/fs/nfsd/nfs4acl.c
> index 6f3f392..de5d66b 100644
> --- a/fs/nfsd/nfs4acl.c
> +++ b/fs/nfsd/nfs4acl.c
> @@ -193,16 +193,9 @@ summarize_posix_acl(struct posix_acl *acl, struct
> posix_acl_summary *pas)
>  {
>  	struct posix_acl_entry *pa, *pe;
> 
> -	/*
> -	 * Only pas.users and pas.groups need initialization; previous
> -	 * posix_acl_valid() calls ensure that the other fields will be
> -	 * initialized in the following loop.  But, just to placate gcc:
> -	 */
>  	memset(pas, 0, sizeof(*pas));
>  	pas->mask = 07;
> 
> -	pe = acl->a_entries + acl->a_count;
> -
>  	FOREACH_ACL_ENTRY(pa, acl, pe) {
>  		switch (pa->e_tag) {
>  			case ACL_USER_OBJ:
> -- 
> 1.9.0
> 

      reply	other threads:[~2014-05-08 16:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 12:56 [PATCH 1/2] NFSD: Cleanup unused comments and codes in summarize_posix_acl Kinglong Mee
2014-04-13 13:12 ` [PATCH] " Kinglong Mee
2014-05-08 16:55   ` J. Bruce Fields [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=20140508165553.GF20976@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=kinglongmee@gmail.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 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).