Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ian Molton <ian@mnementh.co.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: add new DAPM control
Date: Wed, 7 Jan 2009 13:57:58 +0000	[thread overview]
Message-ID: <20090107135757.GA12359@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <49641588.7050703@mnementh.co.uk>

On Wed, Jan 07, 2009 at 02:38:00AM +0000, Ian Molton wrote:

> The attached patch adds a new mixer control that allows cleaner support
> for the wm9705 codec Im working on. I think it probably has wider uses
> though.

Applied, thanks.

It'd be handy if you could post patches in the format suggested by
Documentation/SubmittingPatches (unless your e-mail client would mangle
them) with descriptive text after the ---.  This helps with automated
tools like git am.

      reply	other threads:[~2009-01-07 13:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07  2:38 [PATCH] ASoC: add new DAPM control Ian Molton
2009-01-07 13:57 ` 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=20090107135757.GA12359@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ian@mnementh.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