Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755515Ab2FNJZs (ORCPT ); Thu, 14 Jun 2012 05:25:48 -0400 Received: from mail-lb0-f174.google.com ([209.85.217.174]:44800 "EHLO mail-lb0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755400Ab2FNJZq convert rfc822-to-8bit (ORCPT ); Thu, 14 Jun 2012 05:25:46 -0400 MIME-Version: 1.0 In-Reply-To: <20120613152045.81ab66d9.akpm@linux-foundation.org> References: <20120613152045.81ab66d9.akpm@linux-foundation.org> Date: Thu, 14 Jun 2012 05:25:44 -0400 Message-ID: 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) From: Luming Yu To: Andrew Morton Cc: LKML , Peter Zijlstra , tglx@linutronix.de, sfr@canb.auug.org.au, jcm@jonmasters.org, linux-next@vger.kernel.org, Ingo Molnar , torvalds@linux-foundation.org, Arnd Bergmann Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1123 Lines: 30 On Wed, Jun 13, 2012 at 6:20 PM, Andrew Morton wrote: > On Tue, 12 Jun 2012 20:57:02 +0800 > Luming Yu 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/