From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: David Henningsson <david.henningsson@canonical.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: alsa-asoc-devel?
Date: Fri, 6 Aug 2010 12:37:21 +0100 [thread overview]
Message-ID: <20100806113721.GC31326@sirena.org.uk> (raw)
In-Reply-To: <4C5BC9E9.2000407@canonical.com>
On Fri, Aug 06, 2010 at 10:38:01AM +0200, David Henningsson wrote:
> There is a lot of asoc traffic on this list, and I assume many people
> following this list are not interested in ASoC patches.
Oh, and please also remember to CC maintainers on mails. This is a
basic thing which applies to pretty much all kernel related lists.
prev parent reply other threads:[~2010-08-06 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 8:38 alsa-asoc-devel? David Henningsson
2010-08-06 10:48 ` alsa-asoc-devel? Liam Girdwood
2010-08-06 11:06 ` alsa-asoc-devel? David Henningsson
2010-08-06 15:53 ` alsa-asoc-devel? Timur Tabi
2010-08-06 11:31 ` alsa-asoc-devel? Mark Brown
2010-08-06 11:37 ` Mark Brown [this message]
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=20100806113721.GC31326@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
/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;
as well as URLs for NNTP newsgroup(s).