From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: David Henningsson <david.henningsson@canonical.com>
Cc: Takashi Iwai <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Plumbers: Please split audio topics into separate sessions
Date: Mon, 6 Aug 2012 20:38:59 +0100 [thread overview]
Message-ID: <20120806193858.GB16199@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50201664.7000804@canonical.com>
On Mon, Aug 06, 2012 at 09:09:24PM +0200, David Henningsson wrote:
> Audio uConf: HD-audio cooking && QA/Testing
> Audio uConf: Expose Routing && DSPs in ASoC
> Audio uConf: Time Alignment && PA on Android
> Please split these three sessions into six. It is better to have a
> little more time than necessary (even if I believe we easily fill 45
> minutes per topic), than having to skip a topic just because the other
> topic took more time than expected.
The two ASoC topics certainly don't need to be split, they're roughly
the same area. I'd be really surprised if the last two were terribly
time consuming individually.
next prev parent reply other threads:[~2012-08-06 19:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 19:09 Plumbers: Please split audio topics into separate sessions David Henningsson
2012-08-06 19:29 ` Takashi Iwai
2012-08-06 20:11 ` David Henningsson
2012-08-06 22:24 ` Mark Brown
2012-08-07 5:58 ` Takashi Iwai
2012-08-07 6:28 ` Vinod Koul
2012-08-07 6:41 ` David Henningsson
2012-08-07 7:11 ` Takashi Iwai
2012-08-07 8:08 ` David Henningsson
2012-08-07 8:35 ` Takashi Iwai
2012-08-07 11:19 ` David Henningsson
2012-08-07 11:15 ` Mark Brown
2012-08-07 11:26 ` David Henningsson
2012-08-07 13:57 ` Mark Brown
2012-08-07 14:04 ` Takashi Iwai
2012-08-07 14:06 ` Mark Brown
2012-08-06 19:38 ` Mark Brown [this message]
2012-08-06 20:14 ` David Henningsson
2012-08-06 21:45 ` Mark Brown
2012-08-07 6:42 ` Vinod Koul
2012-08-07 7:14 ` Takashi Iwai
2012-08-07 14:07 ` Mark Brown
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=20120806193858.GB16199@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--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.