From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Frederic Weisbecker <fweisbec@gmail.com>, Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] tracing: make splice_read work when data is sufficient
Date: Tue, 01 Sep 2009 20:29:53 +0800 [thread overview]
Message-ID: <4A9D13C1.4030902@cn.fujitsu.com> (raw)
In-Reply-To: <20090829094503.GA6418@nowhere>
Frederic Weisbecker wrote:
>> */
>> + cpu_buffer->reader_page->read = 0;
>
>
>
> Wasn't this reset done before?
>
>
This is not reset. It is still used just before this line.
>
>
> Reviewed-by: Frederic Weisbecker <fweisbec@gmail.com>
>
>
Ingo, Could you apply this patch and fix the bug?
next prev parent reply other threads:[~2009-09-01 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 3:02 [PATCH 1/3] tracing: make splice_read work when data is sufficient Lai Jiangshan
2009-08-29 9:45 ` Frederic Weisbecker
2009-09-01 12:29 ` Lai Jiangshan [this message]
2009-09-01 22:37 ` Frederic Weisbecker
2009-09-02 7:37 ` Lai Jiangshan
2009-09-09 20:51 ` Steven Rostedt
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=4A9D13C1.4030902@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=fweisbec@gmail.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