linux-kernel - Re: [PATCH] staging/zram: Fix sparse warning 'Using plain integer as NULL 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]

Message-ID: <4D000AFE.2090606@vflare.org>
Date:	Wed, 08 Dec 2010 17:47:26 -0500
From:	Nitin Gupta <ngupta@...are.org>
To:	Greg KH <greg@...ah.com>
CC:	Peter Huewe <peterhuewe@....de>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Pekka Enberg <penberg@...helsinki.fi>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging/zram: Fix sparse warning 'Using plain integer
 as NULL pointer'

On 12/8/2010 5:30 PM, Greg KH wrote:
> On Tue, Dec 07, 2010 at 06:09:22PM -0500, Nitin Gupta wrote:
>> On 12/7/2010 5:44 PM, Peter Huewe wrote:
>>> This patch fixes the warning generated by sparse: "Using plain integer
>>> as NULL pointer" by replacing the offending 0s with NULL.
>>>
>>> Signed-off-by: Peter Huewe <peterhuewe@....de>
>>
>> Thanks for the fix. I see that it's already fixed in the
>> project internal repo but I somehow missed sending it to
>> mainline.
> 
> Are you ever going to sync your internal repo with the in-kernel one, or
> should I just delete the in-kernel one?
> 


It is almost sync'ed up (apart from "scalability enhancements") but I
somehow missed this part. Currently, I'm completely occupied with
final exams due next week. So, please be patient.

I plan to completely discard scalability part and solve outstanding
crash reports (http://code.google.com/p/compcache/issues/list) once
this school overhead is over.

Thanks,
Nitin

--
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/