From: Frederic Weisbecker <fweisbec@gmail.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] ring_buffer: fix warning
Date: Tue, 14 Jul 2009 16:15:47 +0200 [thread overview]
Message-ID: <20090714141544.GA5728@nowhere> (raw)
In-Reply-To: <4A5C3549.7000905@cn.fujitsu.com>
On Tue, Jul 14, 2009 at 03:35:37PM +0800, Lai Jiangshan wrote:
>
> kernel/trace/ring_buffer.c: In function 'rb_tail_page_update':
> kernel/trace/ring_buffer.c:849: warning: value computed is not used
> kernel/trace/ring_buffer.c:850: warning: value computed is not used
>
> Add a "(void)" to fix this warning.
>
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> ---
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index e648ba4..d371279 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -846,8 +846,8 @@ static int rb_tail_page_update(struct ring_buffer_per_cpu *cpu_buffer,
> * not come in and change it. In which case, we
> * do not want to modify it.
> */
> - local_cmpxchg(&next_page->write, old_write, val);
> - local_cmpxchg(&next_page->entries, old_entries, eval);
> + (void)local_cmpxchg(&next_page->write, old_write, val);
> + (void)local_cmpxchg(&next_page->entries, old_entries, eval);
>
> /*
> * No need to worry about races with clearing out the commit.
Looks good. Indeed the rest of the path remains the same, whether the
interrupts have already won the race or not.
Reviewed-by: Frederic Weisbecker <fweisbec@gmail.com>
next prev parent reply other threads:[~2009-07-14 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 7:35 [PATCH -tip] ring_buffer: fix warning Lai Jiangshan
2009-07-14 14:15 ` Frederic Weisbecker [this message]
2009-07-14 22:43 ` Steven Rostedt
2009-07-15 8:17 ` [PATCH -tip] ring_buffer: fix warning (V2) Lai Jiangshan
2009-07-15 8:27 ` [PATCH -tip V2] ring_buffer: fix warning Lai Jiangshan
2009-07-16 16:10 ` Frederic Weisbecker
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=20090714141544.GA5728@nowhere \
--to=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/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