From: Steven Rostedt <rostedt@goodmis.org>
To: Thiago Farina <tfransosi@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Li Zefan <lizf@cn.fujitsu.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] trace/trace_output.c: fix "integer as NULL pointer" warning.
Date: Mon, 25 Jan 2010 16:40:31 -0500 [thread overview]
Message-ID: <1264455631.31321.433.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1264349038-1766-3-git-send-email-tfransosi@gmail.com>
On Sun, 2010-01-24 at 11:03 -0500, Thiago Farina wrote:
> kernel/trace/trace_output.c:256:24: warning: Using plain integer as NULL pointer
>
> Signed-off-by: Thiago Farina <tfransosi@gmail.com>
Is this going through some other tree, or should I just pull it?
-- Steve
> ---
> kernel/trace/trace_output.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/trace/trace_output.c b/kernel/trace/trace_output.c
> index 8e46b33..2404c12 100644
> --- a/kernel/trace/trace_output.c
> +++ b/kernel/trace/trace_output.c
> @@ -253,7 +253,7 @@ void *trace_seq_reserve(struct trace_seq *s, size_t len)
> void *ret;
>
> if (s->full)
> - return 0;
> + return NULL;
>
> if (len > ((PAGE_SIZE - 1) - s->len)) {
> s->full = 1;
next prev parent reply other threads:[~2010-01-25 21:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 16:03 [PATCH 1/4] kernel/kfifo.c: fix "interger " 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 [this message]
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 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
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=1264455631.31321.433.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®