Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: fix params_rate() macro use in several codecs
Date: Thu, 24 Dec 2009 12:08:56 +0000	[thread overview]
Message-ID: <20091224120855.GA29968@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0912240109540.4280@axis700.grange>

On Thu, Dec 24, 2009 at 01:13:51AM +0100, Guennadi Liakhovetski wrote:
> Sevelar ASoC codec drivers wrongly assume, that the params_rate() macro 
> returns one of SNDRV_PCM_RATE_* defines instead of the actual numerical 
> sampling rate. Fix them.
> 
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>

Applied, thanks.

      parent reply	other threads:[~2009-12-24 12:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0912240109540.4280@axis700.grange>
2009-12-24  9:46 ` [PATCH] ASoC: fix params_rate() macro use in several codecs Liam Girdwood
2009-12-24 12:08 ` 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=20091224120855.GA29968@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=lrg@slimlogic.co.uk \
    /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