From: Mark Brown <broonie@kernel.org>
To: Curtis Malainey <cujomalainey@google.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Takashi Iwai <tiwai@suse.de>,
ALSA development <alsa-devel@alsa-project.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [alsa-devel] [ANNOUNCE] 2019 Linux Audio miniconference
Date: Tue, 15 Oct 2019 21:11:42 +0100 [thread overview]
Message-ID: <20191015201142.GF4030@sirena.co.uk> (raw)
In-Reply-To: <CAOReqxgt6VM_ZVUJLQk=DSKdNgCxSB40sM0bxyQ6xkMLPGJPSQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 196 bytes --]
On Mon, Oct 14, 2019 at 01:16:40PM -0700, Curtis Malainey wrote:
> Are we going to get a whatsApp chat going beforehand again like last year?
Seems sensible, will ping off-list nearer the time.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
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-15 20:13 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
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 [this message]
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=20191015201142.GF4030@sirena.co.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cujomalainey@google.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.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