From: Mike Frysinger <vapier.adi@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org, akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH v4] ftrace: document basic ftracer/ftracer graph needs
Date: Sun, 13 Sep 2009 21:54:28 -0400 [thread overview]
Message-ID: <8bd0f97a0909131854l511fbcb8ve8b66a5f3b3d2113@mail.gmail.com> (raw)
In-Reply-To: <20090623134319.GC3026@elte.hu>
On Tue, Jun 23, 2009 at 09:43, Ingo Molnar wrote:
> * Mike Frysinger wrote:
>> On Sat, Jun 13, 2009 at 23:05, Mike Frysinger wrote:
>> > While implementing ftracer and ftracer graph support, I found the exact
>> > arch implementation details to be a bit lacking (and my x86 foo ain't
>> > great). So after pounding out support for the Blackfin arch, start
>> > documenting the requirements/details.
>>
>> Steven: were you going to pick this up ? or should i forward to Andrew ?
>
> The .32 development window for the tracing tree starts in about a
> week. We'll probably fast-track your documentation bits to mainline
> - but until then we try to watch for regressions and make sure -rc1
> is round.
unless i missed something, this wasnt picked up
-mike
next prev parent reply other threads:[~2009-09-14 1:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 8:48 [PATCH 1/2] ftrace.txt: fix typo in function grapher name Mike Frysinger
2009-06-10 8:48 ` [PATCH 2/2] ftrace: document basic ftracer/ftracer graph needs Mike Frysinger
2009-06-10 17:04 ` Steven Rostedt
2009-06-10 18:31 ` Mike Frysinger
2009-06-10 18:45 ` Steven Rostedt
2009-06-10 19:07 ` Mike Frysinger
2009-06-10 19:11 ` Steven Rostedt
2009-06-10 19:19 ` Mike Frysinger
2009-06-10 19:34 ` Steven Rostedt
2009-06-10 19:45 ` Mike Frysinger
2009-06-10 18:56 ` Steven Rostedt
2009-06-10 20:52 ` [PATCH 2/2 v2] " Mike Frysinger
2009-06-12 8:10 ` Mike Frysinger
2009-06-13 22:24 ` Frederic Weisbecker
2009-06-14 0:21 ` [PATCH v3] " Mike Frysinger
2009-06-14 1:24 ` Frederic Weisbecker
2009-06-14 1:52 ` Mike Frysinger
2009-06-14 2:24 ` Frederic Weisbecker
2009-06-14 3:05 ` [PATCH v4] " Mike Frysinger
2009-06-14 13:35 ` Frederic Weisbecker
2009-06-23 12:30 ` Mike Frysinger
2009-06-23 13:43 ` Ingo Molnar
2009-09-14 1:54 ` Mike Frysinger [this message]
2009-09-14 2:35 ` Steven Rostedt
2009-09-14 19:48 ` Steven Rostedt
2009-09-14 20:21 ` Mike Frysinger
2009-09-14 20:53 ` Steven Rostedt
2009-09-14 21:01 ` Mike Frysinger
2009-09-14 21:20 ` Steven Rostedt
2009-09-14 21:30 ` Mike Frysinger
2009-09-14 21:41 ` Steven Rostedt
2009-09-14 20:28 ` Frederic Weisbecker
2009-09-15 0:10 ` [PATCH v5] " Mike Frysinger
2009-09-15 1:48 ` [PATCH] [GIT PULL] " Steven Rostedt
2009-09-17 7:47 ` [tip:tracing/core] ftrace: document function and function graph implementation tip-bot for Mike Frysinger
2009-06-14 15:10 ` [PATCH 2/2 v2] ftrace: document basic ftracer/ftracer graph needs Wu Zhangjin
2009-06-14 15:45 ` Mike Frysinger
2009-06-14 16:09 ` Wu Zhangjin
2009-06-15 6:25 ` Mike Frysinger
2009-06-10 17:02 ` [PATCH 1/2] ftrace.txt: fix typo in function grapher name Steven Rostedt
2009-06-10 17:08 ` [PATCH][GIT PULL] ftrace/documentation: " Steven Rostedt
2009-06-10 22:33 ` [tip:tracing/core] " tip-bot for Mike Frysinger
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=8bd0f97a0909131854l511fbcb8ve8b66a5f3b3d2113@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--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
all inboxes | Powered by JetHome®