Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757538AbZLNP10 (ORCPT ); Mon, 14 Dec 2009 10:27:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757526AbZLNP10 (ORCPT ); Mon, 14 Dec 2009 10:27:26 -0500 Received: from cantor2.suse.de ([195.135.220.15]:47636 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757525AbZLNP1Z (ORCPT ); Mon, 14 Dec 2009 10:27:25 -0500 Date: Mon, 14 Dec 2009 07:27:20 -0800 From: Greg KH To: Masa Cc: Oliver Neukum , Alejandro Riveira Fern?ndez , 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? Message-ID: <20091214152720.GA16597@suse.de> References: <20091214122649.2d914941@varda> <200912141536.14266.oliver@neukum.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1000 Lines: 26 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 -- 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/