Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [GIT PULL] fixes for wrong DB_RANGE_HEADER sizes
Date: Mon, 21 Nov 2011 11:30:27 +0000	[thread overview]
Message-ID: <20111121113027.GC3784@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4EC97783.60305@ladisch.de>

On Sun, Nov 20, 2011 at 10:56:19PM +0100, Clemens Ladisch wrote:

> This patch series fixes several drivers where TLV_DB_RANGE_HEAD() was
> used with a wrong number of entries, which resulted in a missing entry
> (in rt5631) or in some surplus entries with random data being returned
> (all other drivers).

Thanks, pulled now.

      reply	other threads:[~2011-11-21 11:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-20 15:21 [GIT PULL] fixes for wrong DB_RANGE_HEADER sizes Clemens Ladisch
2011-11-20 21:02 ` Mark Brown
2011-11-20 21:56   ` Clemens Ladisch
2011-11-21 11:30     ` 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=20111121113027.GC3784@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.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