All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Harsha, Priya" <priya.harsha@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: submitting patches to ALSA
Date: Sat, 20 Jun 2009 08:37:03 +0530	[thread overview]
Message-ID: <98769532B4BB14429434178695419EAE5B7F85FD@bgsmsx501.gar.corp.intel.com> (raw)
In-Reply-To: <s5hws78emcn.wl%tiwai@suse.de>

Thanks Takashi.

I have tested it already with aplay, papaly and firefox flash, etc,.

Regarding the firmware binary, need I send it as a part of the patch in the email or can I be upload it in a common location where anyone can access it?

Also, I am waiting for few dependant drivers to be submitted for upstream before I can submit my patches otherwise it would break.

Thanks,
Harsha



-----Original Message-----
From: alsa-devel-bounces@alsa-project.org [mailto:alsa-devel-bounces@alsa-project.org] On Behalf Of Takashi Iwai
Sent: Friday, June 19, 2009 12:34 PM
To: Harsha, Priya
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] submitting patches to ALSA

At Thu, 18 Jun 2009 21:33:54 +0530,
Harsha, Priya wrote:
> 
> Hi,
> 
> This is the first time I am planning to submit patches to ALSA. Are
> there any tips/rules I need to follow?

In general, the rule for LKML is applied here, too.

> I have followed the general guidelines like checkpatch, testing with
> different debug configs etc.

Great.

> I have a few questions;
> 1. Against which kernel tree should I create patches to submit to
> ALSA devel mailing list?

Try to apply always to the latest tree, e.g. sound git tree below
	git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git

> 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

The firmware file would be either in alsa-firmware package or in
linux-firmware package.  First you can put it to alsa-firmware
package, and we can push them to the upstream linux-firmware package
once after your driver gets merged.

> 3. Is there anything else I need to send to the mailing list in
> addition to the patches?

A good series of patches is self-explanatory :)

> 4. Are there any test suits that I can use to test the driver?

It's a timely question.  We want to discuss this, especially per
request from LSB.  In short answer: no test suits for the time being.
Most people tested with aplay and speaker-test as standard test
programs.


thanks,

Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2009-06-20  3:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 11:49 Indirect Callback with ack is called with no data Singaravelan Nallasellan
2009-06-08 13:51 ` Harsha, Priya
2009-06-11  6:57   ` Harsha, Priya
2009-06-18 16:03 ` submitting patches to ALSA Harsha, Priya
2009-06-19  7:03   ` Takashi Iwai
2009-06-20  3:07     ` Harsha, Priya [this message]
2009-06-20  7:31       ` Takashi Iwai
2009-06-22  7:04         ` Harsha, Priya
2009-06-22  7:07           ` Takashi Iwai
2009-06-23  8:06             ` Harsha, Priya
2009-06-23 11:16               ` Takashi Iwai

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=98769532B4BB14429434178695419EAE5B7F85FD@bgsmsx501.gar.corp.intel.com \
    --to=priya.harsha@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.