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] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 5 Sep 2015 21:21:58 +0200
From:	Anders Fridlund <anders.fridlund@...il.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	devel@...verdev.osuosl.org, christian.gromm@...rochip.com,
	linux-kernel@...r.kernel.org,
	Michael Hornung <mhornung.linux@...il.com>
Subject: Re: [PATCH] staging: most: Use NULL instead of 0 in assignment of pointer

I resent it since no one responded to it for 10 days. From what I came
to understand that is the common practice. If that is not the case I'm
sorry (and please let me know so I don't do it again).

Cheers,
Anders Fridlund

On Thu, Sep 3, 2015 at 6:41 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
> On Sat, Aug 29, 2015 at 01:53:49PM +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
>
> Why did you resend this patch again?
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ