linux-kernel - Re: [PATCH] staging/most: Use NULL instead of plain integer for 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 3 Sep 2015 09:42:10 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Rocco Folino <rocco@...zen.net>
Cc:	christian.gromm@...rochip.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging/most: Use NULL instead of plain integer for
 pointer

On Sat, Aug 22, 2015 at 12:41:54AM +0200, Rocco Folino wrote:
> This patch fixes the warning generated by sparse: "Using plain integer
> as NULL pointer" by replacing 0s with NULL.
> 
> Signed-off-by: Rocco Folino <rocco@...zen.net>
> ---
>  drivers/staging/most/aim-network/networking.c | 2 +-
>  drivers/staging/most/aim-v4l2/video.c         | 2 +-
>  drivers/staging/most/hdm-dim2/dim2_hdm.c      | 8 ++++----
>  3 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/staging/most/aim-network/networking.c b/drivers/staging/most/aim-network/networking.c
> index c8ab2399faad..a1e1bce16296 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;
>  }

Someone sent a patch already that did this change, so this patch doesn't
apply anymore :(
--
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/