From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Jovi Zhangwei <jovi.zhangwei@gmail.com>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
"Ingo Molnar" <mingo@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"zhangwei(Jovi)" <jovi.zhangwei@huawei.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"Tom Zanussi" <tom.zanussi@linux.intel.com>,
"Namhyung Kim" <namhyung@kernel.org>,
"David Ahern" <dsahern@gmail.com>, "Jiri Olsa" <jolsa@redhat.com>
Subject: Re: ktap inclusion in drivers/staging/?
Date: Thu, 24 Oct 2013 16:46:47 -0300 [thread overview]
Message-ID: <20131024194647.GF4998@ghostprotocols.net> (raw)
In-Reply-To: <CAGdX0WG1gmC-ZXn5BFRMD5FM2r5d3oxvDU61-xFrT90badv3tg@mail.gmail.com>
Em Thu, Oct 24, 2013 at 08:11:36PM +0800, Jovi Zhangwei escreveu:
> I admit there have many places need to cleanup in ktap code, and there
> also have a long todo list, I will finish it before start review process.
>
> Again, really sorry for this, please forgive me this mistake.
Just go eroding it, try to figure out things that could be useful on its
own, find the right place in the tree, send a flow of small self
contained patches that comes with tooling that uses whatever new kernel
feature that is added.
I think that even if you just add a 'perf test' entry that shows how the
new feature should be used by tooling, exercising it and checking its
results, so that every time people try 'perf test' it gets re verified,
that would be ok when no other tools/ living source code exercises it.
- Arnaldo
next prev parent reply other threads:[~2013-10-24 19:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 7:58 ktap inclusion in drivers/staging/? Ingo Molnar
2013-10-24 8:46 ` Steven Rostedt
2013-10-24 9:42 ` Linus Torvalds
2013-10-24 10:04 ` Greg Kroah-Hartman
2013-10-25 10:10 ` Ingo Molnar
2013-10-24 9:49 ` Greg Kroah-Hartman
2013-10-24 12:44 ` Jovi Zhangwei
2013-10-24 12:11 ` Jovi Zhangwei
2013-10-24 12:25 ` Steven Rostedt
2013-10-24 19:46 ` Arnaldo Carvalho de Melo [this message]
2013-10-25 3:00 ` Jovi Zhangwei
2013-10-24 12:32 ` Jovi Zhangwei
2013-10-25 10:15 ` Ingo Molnar
2013-10-26 5:02 ` Jovi Zhangwei
2013-10-26 8:59 ` Ingo Molnar
2013-10-28 12:12 ` Masami Hiramatsu
2013-10-28 12:19 ` Ingo Molnar
2013-10-28 12:16 ` Masami Hiramatsu
2013-10-28 13:19 ` Jovi Zhangwei
2013-10-28 5:48 ` Masami Hiramatsu
2013-10-25 11:25 ` Pekka Enberg
2013-10-25 11:34 ` 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=20131024194647.GF4998@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jolsa@redhat.com \
--cc=jovi.zhangwei@gmail.com \
--cc=jovi.zhangwei@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).