All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Masa <masa.korg@gmail.com>
Cc: Oliver Neukum <oliver@neukum.org>,
	Alejandro Riveira Fern?ndez <ariveira@gmail.com>,
	linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [How to upload our driver to "kernel.org"] Would you give me your advice?
Date: Mon, 14 Dec 2009 07:27:20 -0800	[thread overview]
Message-ID: <20091214152720.GA16597@suse.de> (raw)
In-Reply-To: <c7ac85d60912140715x232f9e3di366d2be1e1cd063b@mail.gmail.com>

On Tue, Dec 15, 2009 at 12:15:58AM +0900, Masa wrote:
> > You don't, technically speaking, upload.
> > You make a patch against a current kernel tree and mail it
> > to the relevant list. Then people will tell you what's wrong with your
> > code and how it should be improved. After you'll have fixed
> > the issues, the maintainer will take your patch and it'll be
> > incorporated into the kernel tree at kernel.org.
> 
> It is a useful information for me.
> I understood the procedure.
> 
> I think that I may take time to solve all issues.
> However, I want to give a TRY.

If you need help with this process, or with cleaning up your code to
make it acceptable, please let us on the devel@linuxdriverproject.org
list help you out.

thanks,

greg k-h

  reply	other threads:[~2009-12-14 15:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 10:56 [How to upload our driver to "kernel.org"] Would you give me your advice? Masa
2009-12-14 11:26 ` Alejandro Riveira Fernández
2009-12-14 12:21   ` Mithlesh Thukral
2009-12-14 14:45     ` Masa
2009-12-14 15:32       ` tytso
2009-12-14 16:02         ` Masa
2009-12-14 14:10   ` Masa
2009-12-14 14:36     ` Oliver Neukum
2009-12-14 15:15       ` Masa
2009-12-14 15:27         ` Greg KH [this message]
2009-12-14 15:43           ` Masa
2009-12-14 15:00   ` Greg KH
2009-12-14 15:30     ` Masa
2009-12-14 13:05 ` Jonathan Corbet
2009-12-14 14:57   ` Masa

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=20091214152720.GA16597@suse.de \
    --to=gregkh@suse.de \
    --cc=ariveira@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masa.korg@gmail.com \
    --cc=oliver@neukum.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.