Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753451Ab2FLOmo (ORCPT ); Tue, 12 Jun 2012 10:42:44 -0400 Received: from mail-ey0-f174.google.com ([209.85.215.174]:37180 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752299Ab2FLOmm (ORCPT ); Tue, 12 Jun 2012 10:42:42 -0400 Message-ID: <1339512147.2099.3.camel@sysadmin.euractiv.com> 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: Jimmy Thrasibule To: Luming Yu Cc: LKML Date: Tue, 12 Jun 2012 16:42:27 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.1 (3.4.1-2.fc17) Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 737 Lines: 20 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 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/