From: Luming Yu <luming.yu@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
tglx@linutronix.de, sfr@canb.auug.org.au, jcm@jonmasters.org,
linux-next@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
torvalds@linux-foundation.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: What is the right practice to get new code upstream( was Fwd: [patch] a simple hardware detector for latency as well as throughput ver. 0.1.0)
Date: Thu, 14 Jun 2012 05:25:44 -0400 [thread overview]
Message-ID: <CAJRGBZy_wqUgN_jx9PinXHSGM30XjrRm49xFXkfumucAeaQ2bw@mail.gmail.com> (raw)
In-Reply-To: <20120613152045.81ab66d9.akpm@linux-foundation.org>
On Wed, Jun 13, 2012 at 6:20 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Tue, 12 Jun 2012 20:57:02 +0800
> Luming Yu <luming.yu@gmail.com> wrote:
>
>> I need to know what the right practice is to get your attention to
>> accept a new tool upstream like this one.
>
> Seems that you have some good feedback from Arnd to be looking at. I'm
> usually the guy for mysterious misc stuff such as this, so please cc me
> on future revisions.
Andrew, Thanks a lot :-) The community is really helpful after find
right people for right things.
>
> The name "hw_test" and "HW_TEST" is too vague. The topic "testing
> hardware" is very broad, and this module only touches a small fraction
> of it, so please think up a far more specific name.
>
I'm working on Version 2 of the tool which would be renamed to
cpu_latency_test, or simply misc_latency_test?
thanks!!! /l
next prev parent reply other threads:[~2012-06-14 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 12:57 What is the right practice to get new code upstream( was Fwd: [patch] a simple hardware detector for latency as well as throughput ver. 0.1.0) Luming Yu
2012-06-13 22:20 ` Andrew Morton
2012-06-14 9:25 ` Luming Yu [this message]
2012-06-14 10:04 ` Peter Zijlstra
2012-06-14 14:15 ` Luming Yu
2012-06-21 13:29 ` Robert Richter
2012-06-21 14:43 ` Peter Zijlstra
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=CAJRGBZy_wqUgN_jx9PinXHSGM30XjrRm49xFXkfumucAeaQ2bw@mail.gmail.com \
--to=luming.yu@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=jcm@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--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).