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 V2] ring_buffer: fix warning
Date: Thu, 16 Jul 2009 12:10:57 -0400 [thread overview]
Message-ID: <20090716161055.GC8043@nowhere> (raw)
In-Reply-To: <4A5D92F2.1010007@cn.fujitsu.com>
On Wed, Jul 15, 2009 at 04:27:30PM +0800, Lai Jiangshan wrote:
> Sorry for missing Reviewed-by and Acked-by, so I resend it.
>
> Subject: [PATCH -tip V2] ring_buffer: fix warning
>
> 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 "(void)"s to fix this warning.
>
> Changed from V1:
> Add a comment(which is written by Steven) for it.
>
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> Reviewed-by: Frederic Weisbecker <fweisbec@gmail.com>
> Acked-by: Steven Rostedt <rostedt@goodmis.org>
Queued for .32, thanks!
> ---
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index e648ba4..51633d7 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -845,9 +845,14 @@ static int rb_tail_page_update(struct ring_buffer_per_cpu *cpu_buffer,
> * This will only succeed if an interrupt did
> * not come in and change it. In which case, we
> * do not want to modify it.
> + *
> + * We add (void) to let the compiler know that we do not care
> + * about the return value of these functions. We use the
> + * cmpxchg to only update if an interrupt did not already
> + * do it for us. If the cmpxchg fails, we don't care.
> */
> - 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.
>
prev parent reply other threads:[~2009-07-16 16:11 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
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 [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=20090716161055.GC8043@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