All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Anders Fridlund <anders.fridlund@gmail.com>
Cc: christian.gromm@microchip.com, mhornung.linux@gmail.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: most: Use NULL instead of 0 in assignment of pointer
Date: Thu, 3 Sep 2015 09:41:24 -0700	[thread overview]
Message-ID: <20150903164124.GA26360@kroah.com> (raw)
In-Reply-To: <1440022372-23891-1-git-send-email-anders.fridlund@gmail.com>

On Thu, Aug 20, 2015 at 12:12:51AM +0200, Anders Fridlund wrote:
> Fix sparse warning 'Using plain integer as NULL pointer' by replacing 0
> with NULL in the assignment.
> 
> Signed-off-by: Anders Fridlund <anders.fridlund@gmail.com>
> ---
>  drivers/staging/most/aim-network/networking.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/most/aim-network/networking.c b/drivers/staging/most/aim-network/networking.c
> index c8ab239..a1e1bce 100644
> --- a/drivers/staging/most/aim-network/networking.c
> +++ b/drivers/staging/most/aim-network/networking.c
> @@ -295,7 +295,7 @@ static void most_net_rm_netdev_safe(struct net_dev_context *nd)
>  
>  	unregister_netdev(nd->dev);
>  	free_netdev(nd->dev);
> -	nd->dev = 0;
> +	nd->dev = NULL;
>  }
>  
>  static struct net_dev_context *get_net_dev_context(
> -- 
> 1.9.1

Someone sent this patch before you did, sorry :(

  reply	other threads:[~2015-09-03 16:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 22:12 [PATCH] staging: most: Use NULL instead of 0 in assignment of pointer Anders Fridlund
2015-09-03 16:41 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-08-29 11:53 Anders Fridlund
2015-09-03 16:41 ` Greg KH
2015-09-05 19:21   ` Anders Fridlund
2015-09-05 20:03     ` Greg KH
2015-09-22 13:07     ` Dan Carpenter

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=20150903164124.GA26360@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=anders.fridlund@gmail.com \
    --cc=christian.gromm@microchip.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhornung.linux@gmail.com \
    /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.