From: Daniel Baluta <daniel.baluta@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>, "S.j. Wang" <shengjiu.wang@nxp.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Curtis Malainey <cujomalainey@google.com>,
Guido Roncarolo <guido.roncarolo@nxp.com>
Subject: Re: [alsa-devel] [ANNOUNCE] 2019 Linux Audio miniconference
Date: Wed, 9 Oct 2019 21:48:14 +0300 [thread overview]
Message-ID: <CAEnQRZAR1b-CHHVEv0ia92vYu38fWkwgW3mdwJFhEQsHk2j5+A@mail.gmail.com> (raw)
In-Reply-To: <20191009181356.GO2036@sirena.org.uk>
On Wed, Oct 9, 2019 at 9:15 PM Mark Brown <broonie@kernel.org> wrote:
>
> Hi,
>
> As in previous years we're going to have an audio miniconference so we can
> get together and talk through issues, especially design decisions, face to
> face. This year's event will be held on October 31st in Lyon, France,
> the day after ELC-E. This will be held at the Lyon Convention Center (the
> ELC-E venue) and will be free of charge to attend, generously
> sponsored by Intel.
>
> Thus far for the agenda we have:
>
> - Use case management enhancements (Curtis)
> - DSP framework integration (Liam?)
> - Soundwire status (Pierre?)
> - Componentisation status/plans (Me)
Hi Mark,
Thanks for taking care of this.
My topics:
- SOF driver: ACPI / DT unification
- SOF driver: Handling built-in driver use case
>
> As with previous years let's pull together an agenda through a mailing
> list discussion - if people could reply to this mail with any topics
> they'd like to discuss we can take it from there. Of course if we can
> sort things out more quickly via the mailing list that's even better!
>
> If you're planning to attend please fill out the form here:
>
> https://docs.google.com/forms/d/e/1FAIpQLSd6FV-tWYZ1fHlCmyzQhG98OtYH9W9GX-1dQ88mnLxVRGyPww/viewform?usp=sf_link
>
> This event will be covered by the same code of conduct as ELC-E.
>
> Thanks again to Intel for supporting this event.
>
> Thanks,
> Mark
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-10-09 18:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 18:13 [alsa-devel] [ANNOUNCE] 2019 Linux Audio miniconference Mark Brown
2019-10-09 18:48 ` Daniel Baluta [this message]
2019-10-10 15:57 ` Mark Brown
2019-10-10 16:43 ` Pierre-Louis Bossart
2019-10-10 19:43 ` Daniel Baluta
2019-10-09 19:16 ` Pierre-Louis Bossart
2019-10-25 10:05 ` Vinod Koul
2019-10-14 19:47 ` Liam Girdwood
2019-10-14 20:16 ` Curtis Malainey
2019-10-15 20:11 ` Mark Brown
2019-10-15 20:11 ` Mark Brown
2019-10-22 18:59 ` Mark Brown
2019-10-23 9:20 ` Jerome Brunet
2019-10-23 16:53 ` Mark Brown
2019-10-24 14:20 ` Patrick Lai
2019-10-24 14:31 ` Pierre-Louis Bossart
2019-10-25 9:45 ` Vinod Koul
2019-10-25 14:27 ` Pierre-Louis Bossart
2019-10-25 17:26 ` Patrick Lai
2019-10-24 19:15 ` 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=CAEnQRZAR1b-CHHVEv0ia92vYu38fWkwgW3mdwJFhEQsHk2j5+A@mail.gmail.com \
--to=daniel.baluta@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cujomalainey@google.com \
--cc=guido.roncarolo@nxp.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=shengjiu.wang@nxp.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 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).