[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJRGBZy_wqUgN_jx9PinXHSGM30XjrRm49xFXkfumucAeaQ2bw@mail.gmail.com>
Date: Thu, 14 Jun 2012 05:25:44 -0400
From: Luming Yu <luming.yu@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>, tglx@...utronix.de,
sfr@...b.auug.org.au, jcm@...masters.org,
linux-next@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
torvalds@...ux-foundation.org, Arnd Bergmann <arnd@...db.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)
On Wed, Jun 13, 2012 at 6:20 PM, Andrew Morton
<akpm@...ux-foundation.org> wrote:
> On Tue, 12 Jun 2012 20:57:02 +0800
> Luming Yu <luming.yu@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists