mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	nfs@lists.sourceforge.net
Subject: Re: [PATCH] - [7/15] - remove defconfig ptr comparisons to 0 - fs/lockd
Date: Wed, 14 Nov 2007 13:40:47 +1100	[thread overview]
Message-ID: <18234.24623.742782.328651@notabene.brown> (raw)
In-Reply-To: message from Joe Perches on Tuesday November 13

On Tuesday November 13, joe@perches.com wrote:
> Remove defconfig ptr comparison to 0
> 
> Remove sparse warning: Using plain integer as NULL pointer
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> 
> ---
> 
> diff --git a/fs/lockd/svcshare.c b/fs/lockd/svcshare.c
> index 068886d..98548ad 100644
> --- a/fs/lockd/svcshare.c
> +++ b/fs/lockd/svcshare.c
> @@ -71,7 +71,7 @@ nlmsvc_unshare_file(struct nlm_host *host, struct nlm_file *file,
>  	struct nlm_share	*share, **shpp;
>  	struct xdr_netobj	*oh = &argp->lock.oh;
>  
> -	for (shpp = &file->f_shares; (share = *shpp) != 0; shpp = &share->s_next) {
> +	for (shpp = &file->f_shares; (share = *shpp); shpp = &share->s_next) {
>  		if (share->s_host == host && nlm_cmp_owner(share, oh)) {
>  			*shpp = share->s_next;
>  			kfree(share);
> 

I particularly disagree with this change as it now looked like it
could be an '==' comparison that was mistyped.  Making it 
        ....; (share = *shpp) != NULL; ....

makes the intent clear.

NeilBrown

  reply	other threads:[~2007-11-14  2:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14  2:05 Joe Perches
2007-11-14  2:40 ` Neil Brown [this message]
2007-11-14  4:45   ` Trond Myklebust
2007-11-14 17:50     ` Trond Myklebust

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=18234.24623.742782.328651@notabene.brown \
    --to=neilb@suse.de \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=torvalds@linux-foundation.org \
    --cc=trond.myklebust@fys.uio.no \
    /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

all inboxes | Powered by JetHome®