From: Andy Owen <andy-alsa@ultra-premium.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH - ca0106 1/6] ALSA: ca0106 - add Sound Blaster 5.1vx info.
Date: Sat, 23 Oct 2010 17:28:57 +1100 [thread overview]
Message-ID: <1287815337.1940.5.camel@marvin> (raw)
In-Reply-To: <s5hy69rb61b.wl%tiwai@suse.de>
On Thu, 2010-10-21 at 23:16 +0200, Takashi Iwai wrote:
> Thanks for patches.
> All changes look good in your patches, but could you give more
> changelog for clarifying a bit more details what the patch is
> actually for?
Sure.
Before I send another round of patches, could I just check that sending
to patch@alsa-project.org and cc-ing alsa-devel@alsa-project.org is
correct. I seem to be the only person double spamming like this, which
I'm doing just because the wiki says to:
http://www.alsa-project.org/main/index.php/GIT_Server#Occasional_Developers
(and if the wiki is out of date, and someone feels like editing it to be
right, then that will save me from having to make an account :)
Andy
next prev parent reply other threads:[~2010-10-23 6:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 12:39 [PATCH - ca0106 1/6] ALSA: ca0106 - add Sound Blaster 5.1vx info Andy Owen
2010-10-21 12:39 ` [PATCH - ca0106 2/6] ALSA: ca0106: Pull out dac powering routine into separate function Andy Owen
2010-10-21 12:39 ` [PATCH - ca0106 3/6] ALSA: ca0106: Move enabling of front dac out of hardcoded setup sequence Andy Owen
2010-10-21 12:39 ` [PATCH - ca0106 4/6] ALSA: ca0106: Create a nice spot for mapping channels to dacs Andy Owen
2010-10-21 12:39 ` [PATCH - ca0106 5/6] ALSA: ca0106: Allow different sound cards to use different SPI channel mappings Andy Owen
2010-10-21 12:39 ` [PATCH - ca0106 6/6] ALSA: ca0106: Use card specific dac id for mute controls Andy Owen
2010-10-21 21:16 ` [PATCH - ca0106 1/6] ALSA: ca0106 - add Sound Blaster 5.1vx info Takashi Iwai
2010-10-23 6:28 ` Andy Owen [this message]
[not found] ` <1287814690.1940.4.camel@marvin>
2010-10-23 9:22 ` 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=1287815337.1940.5.camel@marvin \
--to=andy-alsa@ultra-premium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox