All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org,
	Charles Keepax <ckeepax@opensource.cirrus.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Takashi Sakamoto <o-takashi@sakamocchi.jp>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Eric Laurent <elaurent@google.com>
Subject: Re: Prague Audio miniconference - draft schedule
Date: Tue, 24 Oct 2017 12:25:09 +0200	[thread overview]
Message-ID: <s5hh8uorgfu.wl-tiwai@suse.de> (raw)
In-Reply-To: <20171024102247.kfmqpzhytkmgpgaw@sirena.org.uk>

On Tue, 24 Oct 2017 12:22:47 +0200,
Mark Brown wrote:
> 
> On Tue, Oct 24, 2017 at 07:04:50PM +0900, Takashi Sakamoto wrote:
> > On Oct 24 2017 17:23, Mark Brown wrote:
> 
> > > I raised this as something we ought to discuss and mentioned that it was
> > > something you'd been bringing up, you didn't say anything so I read your
> > > other suggestions as additional topics.  If you don't want to discuss it
> > > I'm not sure how much there is to discuss as everyone else seemed pretty
> > > happy with the status quo, though there was Charles' proposed patch
> > > which we were going to cover.
> 
> > Just work for what you proposed by yourself, Mark.
> 
> OK...  so does anyone actually want to talk about this then?

Hm, I thought Charles proposed that?

I'd like to see a consensus for the direction we'll be heading, at
least.


thanks,

Takashi

  reply	other threads:[~2017-10-24 10:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 12:44 Prague Audio miniconference - draft schedule Mark Brown
2017-10-24  1:41 ` Takashi Sakamoto
2017-10-24  8:23   ` Mark Brown
2017-10-24 10:04     ` Takashi Sakamoto
2017-10-24 10:22       ` Mark Brown
2017-10-24 10:25         ` Takashi Iwai [this message]
2017-10-24 10:29           ` 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=s5hh8uorgfu.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=elaurent@google.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=o-takashi@sakamocchi.jp \
    --cc=peter.ujfalusi@ti.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.