Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753392Ab2FLO5X (ORCPT ); Tue, 12 Jun 2012 10:57:23 -0400 Received: from mail-lpp01m010-f46.google.com ([209.85.215.46]:52917 "EHLO mail-lpp01m010-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753255Ab2FLO5U (ORCPT ); Tue, 12 Jun 2012 10:57:20 -0400 MIME-Version: 1.0 In-Reply-To: <1339512147.2099.3.camel@sysadmin.euractiv.com> References: <1339512147.2099.3.camel@sysadmin.euractiv.com> Date: Tue, 12 Jun 2012 22:57:18 +0800 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: Jimmy Thrasibule Cc: LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1153 Lines: 29 On Tue, Jun 12, 2012 at 10:42 PM, Jimmy Thrasibule wrote: > On Tue, 2012-06-12 at 20:57 +0800, Luming Yu wrote: >> Hi All, >> >> I must have forgotten cc key persons. Sorry to make noise again. >> I need to know what the right practice is to get your attention to >> accept a new tool upstream like this one. > Might good to have a look at the following: > > http://www.kernel.org/doc/Documentation/SubmittingPatches > http://www.kernel.org/doc/Documentation/SubmitChecklist > http://www.linuxfoundation.org/content/how-participate-linux-community Thanks for these pointers, they are useful. My intention is to push the initial working version into -mm.Then continuously improve bits by bits. The first version works at minimal level as a tool. So I requested it merges into linux-next or -mm. as the first step to find way upstream. Any advise on this? > > Regards, > Jimmy > -- 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/