From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jarkko.nikula@nokia.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Using ARRAY_SIZE macro when setting up ASoC audio map?
Date: Wed, 27 Feb 2008 22:01:22 +0000 [thread overview]
Message-ID: <20080227220121.GA5414@sirena.org.uk> (raw)
In-Reply-To: <20080227151151.547a3669.jarkko.nikula@nokia.com>
On Wed, Feb 27, 2008 at 03:11:51PM +0200, Jarkko Nikula wrote:
> Ok. Probably not worth to change now to n different drivers but worth
> to take into account when reviewing new ones or doing some other
> cleanups.
For ASoC v2 we've been adding bulk registration functions for everything
which should encourage that. This hasn't been done for paths yet but
that should be done shortly.
next prev parent reply other threads:[~2008-02-27 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 11:49 Using ARRAY_SIZE macro when setting up ASoC audio map? Jarkko Nikula
2008-02-27 12:34 ` Mark Brown
2008-02-27 13:11 ` Jarkko Nikula
2008-02-27 22:01 ` Mark Brown [this message]
2008-02-27 16:15 ` Takashi Iwai
2008-02-28 7:15 ` Jarkko Nikula
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=20080227220121.GA5414@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jarkko.nikula@nokia.com \
/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