alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Richard Fitzgerald <rf@opensource.wolfsonmicro.com>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 0/9] ASoC: wm*: Fix enum ctl accesses
Date: Tue, 8 Mar 2016 09:02:56 +0000	[thread overview]
Message-ID: <20160308090256.GF1490@localhost.localdomain> (raw)
In-Reply-To: <1456765278-5435-1-git-send-email-tiwai@suse.de>

On Mon, Feb 29, 2016 at 06:01:09PM +0100, Takashi Iwai wrote:
> Hi,
> 
> here is a patchset for correcting the wrong access types to the enum
> ctl values in various wm* codec drivers.
> 
> I didn't put Cc to stable.  If they might be used for 64 bit
> architectures, it's a real problem.  In that case, feel free to put Cc
> to stable.
> 
> 
> thanks,
> 
> Takashi
> 
> ===

For the whole series:

Acked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>

Thanks,
Charles

      parent reply	other threads:[~2016-03-08  9:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 17:01 [PATCH 0/9] ASoC: wm*: Fix enum ctl accesses Takashi Iwai
2016-02-29 17:01 ` [PATCH 1/9] ASoC: wm8753: Fix enum ctl accesses in a wrong type Takashi Iwai
2016-03-01  3:21   ` Applied "ASoC: wm8753: Fix enum ctl accesses in a wrong type" to the asoc tree Mark Brown
2016-02-29 17:01 ` [PATCH 2/9] ASoC: wm8904: Fix enum ctl accesses in a wrong type Takashi Iwai
2016-03-01  3:21   ` Applied "ASoC: wm8904: Fix enum ctl accesses in a wrong type" to the asoc tree Mark Brown
2016-02-29 17:01 ` [PATCH 3/9] ASoC: wm8958: Fix enum ctl accesses in a wrong type Takashi Iwai
2016-03-01  3:21   ` Applied "ASoC: wm8958: Fix enum ctl accesses in a wrong type" to the asoc tree Mark Brown
2016-02-29 17:01 ` [PATCH 4/9] ASoC: wm8983: Fix enum ctl accesses in a wrong type Takashi Iwai
2016-03-01  3:20   ` Applied "ASoC: wm8983: Fix enum ctl accesses in a wrong type" to the asoc tree Mark Brown
2016-02-29 17:01 ` [PATCH 5/9] ASoC: wm8985: Fix enum ctl accesses in a wrong type Takashi Iwai
2016-03-01  3:20   ` Applied "ASoC: wm8985: Fix enum ctl accesses in a wrong type" to the asoc tree Mark Brown
2016-02-29 17:01 ` [PATCH 6/9] ASoC: wm8994: Fix enum ctl accesses in a wrong type Takashi Iwai
2016-03-01  3:19   ` Applied "ASoC: wm8994: Fix enum ctl accesses in a wrong type" to the asoc tree Mark Brown
2016-02-29 17:01 ` [PATCH 7/9] ASoC: wm8996: Fix enum ctl accesses in a wrong type Takashi Iwai
2016-03-01  3:19   ` Applied "ASoC: wm8996: Fix enum ctl accesses in a wrong type" to the asoc tree Mark Brown
2016-02-29 17:01 ` [PATCH 8/9] ASoC: wm9081: Fix enum ctl accesses in a wrong type Takashi Iwai
2016-03-01  3:19   ` Applied "ASoC: wm9081: Fix enum ctl accesses in a wrong type" to the asoc tree Mark Brown
2016-02-29 17:01 ` [PATCH 9/9] ASoC: wm_adsp: Fix enum ctl accesses in a wrong type Takashi Iwai
2016-03-01  3:19   ` Applied "ASoC: wm_adsp: Fix enum ctl accesses in a wrong type" to the asoc tree Mark Brown
2016-03-08  9:02 ` Charles Keepax [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=20160308090256.GF1490@localhost.localdomain \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=rf@opensource.wolfsonmicro.com \
    --cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).