All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Adam Rosenberg <adam@alcorn.com>,
	alsa-devel@alsa-project.org, Sonic Zhang <Sonic.Zhang@analog.com>,
	Barry Song <21cnbao@gmail.com>, Cliff Cai <cliff.cai@analog.com>
Subject: Re: Problem with underrun on new CS42448 x2 driver
Date: Fri, 27 Aug 2010 19:00:30 -0400	[thread overview]
Message-ID: <201008271900.32511.vapier@gentoo.org> (raw)
In-Reply-To: <20100827212019.GA7399@opensource.wolfsonmicro.com>


[-- Attachment #1.1: Type: Text/Plain, Size: 1131 bytes --]

On Friday, August 27, 2010 17:20:25 Mark Brown wrote:
> On Fri, Aug 27, 2010 at 04:37:45PM -0400, Mike Frysinger wrote:
> > On Thu, Aug 26, 2010 at 14:06, Adam Rosenberg wrote:
> > > Thank you for the reply.  I emailed Barry Song on July 30th to request
> > > some help moving to the new ASoC standards but received no response.
> > 
> > developers shouldnt be e-mailed directly ... it isnt uncommon for them
> > to simply be punted.  this is why we have mailing lists and forums.
> 
> That's shouldn't *only* be e-mailed directly (for Linux stuff).  You
> should generally keep the relevant folks in the CC as well but also mail
> the lists concerned.  The direct mail is there because the lists can be
> high volume so it helps people see the mail, while the lists mean that
> people other than those you thought of will be able to help and that any
> answers will be archived for other people who might need them.

right of course.  i meant e-mailing people directly and not including lists.

for Blackfin issues, we have a mailing list that should always be CC-ed 
whenever the Blackfin is involved.
-mike

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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

      reply	other threads:[~2010-08-27 23:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24 19:47 Problem with underrun on new CS42448 x2 driver Adam Rosenberg
2010-08-26 12:47 ` Mark Brown
2010-08-26 18:06   ` Adam Rosenberg
2010-08-26 18:52     ` Mark Brown
2010-08-27 20:11       ` Adam Rosenberg
2010-08-27 22:04         ` Mark Brown
2010-08-27 20:37     ` Mike Frysinger
2010-08-27 21:20       ` Mark Brown
2010-08-27 23:00         ` Mike Frysinger [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=201008271900.32511.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=21cnbao@gmail.com \
    --cc=Sonic.Zhang@analog.com \
    --cc=adam@alcorn.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cliff.cai@analog.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 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.