All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Status of UCM
Date: Thu, 21 Oct 2010 22:20:32 +0100	[thread overview]
Message-ID: <1287696032.3205.79.camel@odin> (raw)
In-Reply-To: <20101018232242.GA25852@opensource.wolfsonmicro.com>

On Mon, 2010-10-18 at 16:22 -0700, Mark Brown wrote:
> On Mon, Oct 18, 2010 at 06:52:34PM +0100, Liam Girdwood wrote:
> 
> > Jaroslav, any update on this ?
> 
> Yes, please.  I was working with a cellphone vendor the other week to
> deploy this and while it was solving real problems for them they had
> some entirely legitimate concerns about the stability of the foundations
> they were building on due to the ongoing review.

Ping.

Anything I can help with here ?

Thanks

Liam
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

      reply	other threads:[~2010-10-21 21:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18 15:09 Status of UCM Tobin Davis
2010-10-18 17:52 ` Liam Girdwood
2010-10-18 23:22   ` Mark Brown
2010-10-21 21:20     ` Liam Girdwood [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=1287696032.3205.79.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=perex@perex.cz \
    /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.