linux-kernel - Re: [PATCH] staging: most: Use NULL instead of 0 in assignment of pointer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150903164124.GA26360@kroah.com>
Date:	Thu, 3 Sep 2015 09:41:24 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Anders Fridlund <anders.fridlund@...il.com>
Cc:	christian.gromm@...rochip.com, mhornung.linux@...il.com,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: most: Use NULL instead of 0 in assignment of
 pointer

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@...il.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 :(
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/