Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Curtis Malainey <cujomalainey@google.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [ANNOUNCE] 2019 Linux Audio miniconference
Date: Thu, 29 Aug 2019 19:40:28 +0100	[thread overview]
Message-ID: <20190829184028.GI4118@sirena.co.uk> (raw)
In-Reply-To: <CAOReqxjCTZosbvv8Q-t5zGdreKnk8nWH2Yq-9soLbOk8FOcsgw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1187 bytes --]

On Thu, Aug 29, 2019 at 10:54:29AM -0700, Curtis Malainey wrote:

> > 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!

> I may be miss reading this but I'm reading that as 'the mailing list'
> or ' the mailing list'. Is there an alternative such as a google doc?

It's the same wording I've cut'n'pasted for several years now!  The
alternatives are that we either put things on the agenda via the mailing
list or work out what to do before the meeting in which case it doesn't
need to go on the agenda.

> I am interested in discussing the possibility of upstreaming some of
> the features we have built into our UCMs locally. With the growing
> number of UCMs being maintained by ALSA upstream we think it would be
> beneficial to get those features upstreamed if the community agrees.

This definitely sounds like a good topic, especially for DSP parameters.
I know there's a few other things out there but as you say nothing
upstream yet.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2019-08-29 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27 20:28 [ANNOUNCE] 2019 Linux Audio miniconference Mark Brown
2019-08-28  8:07 ` Liam Girdwood
2019-08-29 17:54 ` Curtis Malainey
2019-08-29 18:40   ` Mark Brown [this message]

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=20190829184028.GI4118@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=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