All of lore.kernel.org
 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>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 000/105] Rename soc_enum.max field
Date: Tue, 18 Feb 2014 15:58:16 +0000	[thread overview]
Message-ID: <20140218155816.GB5438@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1392722967-12472-1-git-send-email-tiwai@suse.de>

On Tue, Feb 18, 2014 at 12:29:24PM +0100, Takashi Iwai wrote:
> Hi,
> 
> this is the first chunk of the whole patch serires, preliminary works
> for renaming the confusing field name and minor clean ups in the
> relevant places.
> 
> After this chunk, SOC_ENUM_*_DECL() macro cleanup and the actual fixes
> for the wrong number of enum items will follow.
> 
> Then introduce SOC_ENUM_SINGLE_CONST() & co for omitting the explicit
> ARRAY_SIZE() call, and apply it in the later patches.
> 
> 
> Takashi

For all the Wolfson related patches:

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

Although as Liam said please feel free to leave it out rather
than editing all the patches.

Thanks,
Charles

  parent reply	other threads:[~2014-02-18 15:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 11:29 [PATCH 000/105] Rename soc_enum.max field Takashi Iwai
2014-02-18 11:29 ` [PATCH 001/102] ASoC: Rename soc_enum.max field with items Takashi Iwai
2014-02-20  1:44   ` Mark Brown
2014-02-18 11:29 ` [PATCH 002/102] ASoC: twl4030: Clean up duplicated code Takashi Iwai
2014-02-20  1:45   ` Mark Brown
2014-02-18 11:29 ` [PATCH 003/102] ALSA: da732x: Remove superfluous DA732X_SOC_ENUM_DOUBLE_R() Takashi Iwai
2014-02-19 16:44   ` Mark Brown
2014-02-18 11:42 ` [PATCH 000/105] Rename soc_enum.max field Takashi Iwai
2014-02-18 13:25 ` Liam Girdwood
2014-02-18 15:58 ` Charles Keepax [this message]
2014-02-18 16:11   ` Lars-Peter Clausen
2014-02-18 16:46 ` Brian Austin

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=20140218155816.GB5438@opensource.wolfsonmicro.com \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.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 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.