From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
vinod.koul@intel.com, "Luis R. Rodriguez" <mcgrof@kernel.org>,
Eric Laurent <elaurent@google.com>
Subject: Re: Audio miniconference at LPC/KS - draft schedule
Date: Fri, 28 Oct 2016 09:01:03 +0100 [thread overview]
Message-ID: <1477641663.19698.6.camel@loki> (raw)
In-Reply-To: <20161027221754.GW25322@sirena.org.uk>
On Thu, 2016-10-27 at 23:17 +0100, Mark Brown wrote:
> which is quite a list but some of those should be fairly simple to
> discuss so hopefully fairly quick. I've made some effort to sort this
> into a rough order but it's very much a first pass so suggestions for
> changes are welcome. Similarly are there are other things people think
> we should discuss?
I can do a short intro and Q&A on Sound Open Firmware for anyone
interested in open source audio DSP firmwares (especially how we can
optimise firmware for ALSA, Pulseaudio, Linux etc).
Thanks
Liam
next prev parent reply other threads:[~2016-10-28 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 22:17 Audio miniconference at LPC/KS - draft schedule Mark Brown
2016-10-28 8:01 ` Liam Girdwood [this message]
2016-10-28 11:47 ` Lars-Peter Clausen
2016-10-28 15:39 ` Mark Brown
2016-10-29 14:05 ` Takashi Sakamoto
2016-10-31 23:39 ` Ughreja, Rakesh A
2016-11-02 8:30 ` Koul, Vinod
2016-11-13 3:33 ` Takashi Sakamoto
2016-11-13 6:09 ` Vinod Koul
2016-11-14 2:01 ` Takashi Sakamoto
2016-11-02 13:17 ` Lars-Peter Clausen
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=1477641663.19698.6.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=elaurent@google.com \
--cc=mcgrof@kernel.org \
--cc=o-takashi@sakamocchi.jp \
--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.