From: Nitin Gupta <ngupta@vflare.org>
To: Greg KH <greg@kroah.com>
Cc: Peter Huewe <peterhuewe@gmx.de>,
Greg Kroah-Hartman <gregkh@suse.de>,
Pekka Enberg <penberg@cs.helsinki.fi>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging/zram: Fix sparse warning 'Using plain integer as NULL pointer'
Date: Wed, 08 Dec 2010 17:47:26 -0500 [thread overview]
Message-ID: <4D000AFE.2090606@vflare.org> (raw)
In-Reply-To: <20101208223051.GB1860@kroah.com>
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@gmx.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
prev parent reply other threads:[~2010-12-08 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 22:44 [PATCH] staging/zram: Fix sparse warning 'Using plain integer as NULL pointer' Peter Huewe
2010-12-07 23:09 ` Nitin Gupta
2010-12-08 22:30 ` Greg KH
2010-12-08 22:47 ` Nitin Gupta [this message]
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=4D000AFE.2090606@vflare.org \
--to=ngupta@vflare.org \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=peterhuewe@gmx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox