All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Girdwood, Liam" <lrg@ti.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
	alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 1/2] ASoC: Allow drivers to specify how many bits are significant on a DAI
Date: Mon, 16 Jan 2012 22:42:40 +0000	[thread overview]
Message-ID: <20120116224238.GA2859@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CABS+qY1rcDjxEcbR6df5mdV4n105Cf_Sis5QOOV6zZG+Sx34gg@mail.gmail.com>

On Mon, Jan 16, 2012 at 10:26:11PM +0000, Girdwood, Liam wrote:

> Btw, will you be reworking Peter's patch ?

Probably if he doesn't get around to it, though I figured that the patch
is so tiny it's probably going to be less work to just write it when
testing rather than to apply a patch from mail so it'd be easier for him
to let him do it.

  reply	other threads:[~2012-01-16 22:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-16 18:41 [PATCH 1/2] ASoC: Allow drivers to specify how many bits are significant on a DAI Mark Brown
2012-01-16 18:41 ` [PATCH 2/2] ASoC: 24 bits are significant on the WM8996 audio interfaces Mark Brown
2012-01-16 22:26 ` [PATCH 1/2] ASoC: Allow drivers to specify how many bits are significant on a DAI Girdwood, Liam
2012-01-16 22:42   ` Mark Brown [this message]
2012-01-17  8:56     ` Peter Ujfalusi
2012-01-17  8:55 ` Peter Ujfalusi
2012-01-17 11:38   ` Mark Brown
2012-01-17 13:06     ` Peter Ujfalusi
2012-01-17 13:19       ` Mark Brown
2012-01-17 14:18         ` Peter Ujfalusi
2012-01-17 14:56           ` Mark Brown
2012-01-17 16:08             ` Peter Ujfalusi
2012-01-17 16:44               ` Mark Brown
2012-01-17 17:55                 ` Peter Ujfalusi
2012-01-17 18:17                   ` Mark Brown
2012-01-17 18:51                     ` Peter Ujfalusi
2012-01-17 18:59                       ` 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=20120116224238.GA2859@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@ti.com \
    --cc=patches@opensource.wolfsonmicro.com \
    --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.