public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jimmy Thrasibule <thrasibule.jimmy@gmail.com>
To: Luming Yu <luming.yu@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
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: Tue, 12 Jun 2012 16:42:27 +0200	[thread overview]
Message-ID: <1339512147.2099.3.camel@sysadmin.euractiv.com> (raw)
In-Reply-To: <CAJRGBZw2TctmBxRuA-byaGNCs=1v+M-1PXSm+OuwWApSqu7UjA@mail.gmail.com>

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


  reply	other threads:[~2012-06-12 14:42 UTC|newest]

Thread overview: 9+ 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-12 14:42 ` Jimmy Thrasibule [this message]
2012-06-12 14:57   ` Luming Yu
2012-06-13 22:20 ` Andrew Morton
2012-06-14  9:25   ` Luming Yu
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=1339512147.2099.3.camel@sysadmin.euractiv.com \
    --to=thrasibule.jimmy@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luming.yu@gmail.com \
    /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