From: Stefani Seibold <stefani@seibold.net>
To: Thiago Farina <tfransosi@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <ak@linux.intel.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] kernel/kfifo.c: fix "interger as NULL pointer" warning.
Date: Wed, 27 Jan 2010 07:44:21 +0100 [thread overview]
Message-ID: <1264574661.18186.0.camel@wall-e> (raw)
In-Reply-To: <a4c8a6d01001261739x2ea25aeev3d5fe596169c7d74@mail.gmail.com>
Am Dienstag, den 26.01.2010, 23:39 -0200 schrieb Thiago Farina:
> Hi Stefani,
>
> On Sun, Jan 24, 2010 at 3:15 PM, Stefani Seibold <stefani@seibold.net> wrote:
> > Am Sonntag, den 24.01.2010, 11:03 -0500 schrieb Thiago Farina:
> >> kernel/kfifo.c:83:35: warning: Using plain integer as NULL pointer
> >>
> >
> > I don't know where you get this kind of warning. But passing 0 for a
> > NULL pointer is ANSI C standard.
>
> NACK?
Acked-by: Stefani Seibold <stefani@seibold.net>
prev parent reply other threads:[~2010-01-27 6:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 16:03 [PATCH 1/4] kernel/kfifo.c: fix "interger as NULL pointer" warning Thiago Farina
2010-01-24 16:03 ` [PATCH 2/4] kernel/test_kprobes.c: fix "integer " Thiago Farina
2010-01-24 16:03 ` [PATCH 3/4] trace/trace_output.c: " Thiago Farina
2010-01-25 21:40 ` Steven Rostedt
2010-05-05 15:59 ` Steven Rostedt
2010-05-07 18:40 ` [tip:tracing/core] tracing: Fix " tip-bot for Thiago Farina
2010-01-24 16:03 ` [PATCH 4/4] mm/memcontrol.c: fix " Thiago Farina
2010-01-24 16:03 ` Thiago Farina
2010-01-24 20:50 ` Balbir Singh
2010-01-24 20:50 ` Balbir Singh
2010-01-24 17:15 ` [PATCH 1/4] kernel/kfifo.c: fix "interger " Stefani Seibold
2010-01-24 18:54 ` Thiago Farina
2010-01-25 10:11 ` Andi Kleen
2010-01-27 1:39 ` Thiago Farina
2010-01-27 6:44 ` Stefani Seibold [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=1264574661.18186.0.camel@wall-e \
--to=stefani@seibold.net \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=tfransosi@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.