From: Mark Brown <broonie@kernel.org>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Liam Girgwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org
Subject: Re: Potential Audio miniconference at LPC/KS
Date: Mon, 22 Aug 2016 11:35:24 +0100 [thread overview]
Message-ID: <20160822103524.GI22076@sirena.org.uk> (raw)
In-Reply-To: <20160822045917.GB2890@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 493 bytes --]
On Mon, Aug 22, 2016 at 10:29:17AM +0530, Vinod Koul wrote:
> On Fri, Aug 12, 2016 at 02:06:16PM +0200, Takashi Iwai wrote:
> > Yeah, that's my concern, too. It'd be great if the situation gets
> > clarified. It seems like the early registration deadline coming
> > soon, and if the LPC registration is mandatory, we'd need to do it
> > ASAP.
> Did we get info from organizers. Audio is still not accepted uConf.
> Anything we missed doing :)
No, they've not communicated anything yet :(
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-08-22 10:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 15:54 Potential Audio miniconference at LPC/KS Mark Brown
2016-07-08 8:59 ` Vinod Koul
2016-07-08 8:54 ` Mark Brown
2016-08-11 6:13 ` Takashi Iwai
2016-08-12 11:26 ` Mark Brown
2016-08-12 12:06 ` Takashi Iwai
2016-08-22 4:59 ` Vinod Koul
2016-08-22 10:35 ` Mark Brown [this message]
2016-08-25 10:38 ` Mark Brown
2016-08-25 15:39 ` Audio miniconference at LPC/KS confirmed- Mark Brown
2016-10-20 13:30 ` Takashi Sakamoto
2016-10-20 14:11 ` Mark Brown
2016-10-21 23:42 ` Takashi Sakamoto
2016-10-22 23:30 ` Mark Brown
2016-10-24 12:57 ` Takashi Sakamoto
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=20160822103524.GI22076@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.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.