From: Steven Rostedt <rostedt@goodmis.org>
To: Pekka Paalanen <pq@iki.fi>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, akpm@osdl.org,
Peter Zijlstra <peterz@infradead.org>,
Soeren Sandmann Pedersen <sandmann@redhat.com>,
Steven Rostedt <srostedt@redhat.com>,
Pavel Roskin <proski@gnu.org>
Subject: Re: [PATCH 0/5] updates to ftrace framework and mmiotrace
Date: Mon, 28 Apr 2008 09:21:15 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0804280920060.813@gandalf.stny.rr.com> (raw)
In-Reply-To: <20080427222925.02b2b27b@daedalus.pq.iki.fi>
On Sun, 27 Apr 2008, Pekka Paalanen wrote:
>
> This resulted in the function trace_seq_to_user() which comes in the
> first patch. Just like the code I refactored, it does not touch filp
> or ppos. I trust the original author better than myself in this one :-)
If you are talking about me as the original author, then I wouldn't trust
me on ppos ;-). I believe I screwed that part up. I'm about to go write
some patches for the read functions now.
-- Steve
next prev parent reply other threads:[~2008-04-28 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 19:29 Pekka Paalanen
2008-04-27 19:33 ` [PATCH 1/5] ftrace: add readpos to struct trace_seq; add trace_seq_to_user() Pekka Paalanen
2008-04-27 19:35 ` [PATCH 2/5] mmiotrace: print header using the read hook Pekka Paalanen
2008-04-27 19:37 ` [PATCH 3/5] mmiotrace: print overrun counts Pekka Paalanen
2008-04-27 19:39 ` [PATCH 4/5] mmiotrace: Do not print bogus pid for maps either Pekka Paalanen
2008-04-27 19:40 ` [PATCH 5/5] doc: update mmiotrace doc to current status Pekka Paalanen
2008-04-28 13:21 ` Steven Rostedt [this message]
2008-04-28 13:29 ` [PATCH 0/5] updates to ftrace framework and mmiotrace Ingo Molnar
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=Pine.LNX.4.58.0804280920060.813@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=pq@iki.fi \
--cc=proski@gnu.org \
--cc=sandmann@redhat.com \
--cc=srostedt@redhat.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®