From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>
Cc: Florian Meier <florian.meier-oZ8rN/sblLk@public.gmane.org>,
Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org
Subject: Re: [alsa-devel] [PATCH] ASoC: pcm512x: Add PCM512x driver
Date: Thu, 6 Feb 2014 13:50:15 +0000 [thread overview]
Message-ID: <20140206135015.GR32298@sirena.org.uk> (raw)
In-Reply-To: <s5hob2kv0z3.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On Thu, Feb 06, 2014 at 02:12:48PM +0100, Takashi Iwai wrote:
> Mark Brown wrote:
> > > The numbers of items in pcm512x_dsp_program_texts[] and _values[]
> > > don't match.
> > Yeah, fixed.
> I'm thinking whether we can check this in the macro.
> I thought of using BUILD_BUG_ON(), but it's unsure whether it aligns
> there well.
Yes, or changing the way we pass things in so it's an array of
key/value. Usability isn't great for enums in general and particularly
poor for sparse ones.
> > Hrm, it is but this points out an error in the control helpers which has
> > been there since forever - they call that parameter max but it's not a
> > maximum, it's the number of elements in the enumeration. I bet we have
> > a bunch of other enumerations which miss the last element as a result.
> Yeah, the argument name is really confusing. I had to double-check
> the code when I reviewed your patch, too :)
> Also it'd be better to have a practice to use either ARRAY_SIZE() or a
> constant there, too.
Indeed - even better would be to just remove the parameter entirely and
use ARRAY_SIZE() on the array of strings we get passed in so there's no
way it could be messed up.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-02-06 13:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 12:26 [PATCH] ASoC: pcm512x: Add PCM512x driver Mark Brown
[not found] ` <1391689575-4039-1-git-send-email-broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2014-02-06 12:51 ` [alsa-devel] " Takashi Iwai
[not found] ` <s5hr47gv1yi.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
2014-02-06 13:07 ` Mark Brown
[not found] ` <20140206130735.GP32298-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-02-06 13:12 ` Takashi Iwai
[not found] ` <s5hob2kv0z3.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
2014-02-06 13:16 ` Lars-Peter Clausen
[not found] ` <52F38B27.1040502-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2014-02-06 13:19 ` Takashi Iwai
2014-02-06 13:50 ` Mark Brown [this message]
2014-02-18 11:22 ` Takashi Iwai
2014-02-23 3:07 ` Mark Brown
2014-02-23 8:29 ` Takashi Iwai
2014-02-24 1:29 ` Mark Brown
2014-02-06 13:24 ` [alsa-devel] " Lars-Peter Clausen
[not found] ` <52F38CF7.7060306-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2014-02-06 14:22 ` Mark Brown
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=20140206135015.GR32298@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=florian.meier-oZ8rN/sblLk@public.gmane.org \
--cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=tiwai-l3A5Bk7waGM@public.gmane.org \
/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