From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Harsha, Priya" Subject: submitting patches to ALSA Date: Thu, 18 Jun 2009 21:33:54 +0530 Message-ID: <98769532B4BB14429434178695419EAE5B719DC3@bgsmsx501.gar.corp.intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by alsa0.perex.cz (Postfix) with ESMTP id A98FE10388A for ; Thu, 18 Jun 2009 18:04:01 +0200 (CEST) Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: "alsa-devel@alsa-project.org" List-Id: alsa-devel@alsa-project.org Hi, This is the first time I am planning to submit patches to ALSA. Are there any tips/rules I need to follow? I have followed the general guidelines like checkpatch, testing with different debug configs etc. I have a few questions; 1. Against which kernel tree should I create patches to submit to ALSA devel mailing list? 2. I have to download firmware as a part of my driver. This firmware file is freely distributable. How should I share the firmware binary file when I send the patches? The firmware binary file would reside in /lib/firmware 3. Is there anything else I need to send to the mailing list in addition to the patches? 4. Are there any test suits that I can use to test the driver? Thanks, Harsha