From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Harsha, Priya" <priya.harsha@intel.com>,
"Bensaid, Selma" <selma.bensaid@intel.com>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: Make register_card API available to drivers
Date: Thu, 13 Jan 2011 11:42:03 +0000 [thread overview]
Message-ID: <20110113114203.GA30351@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <438BB0150E931F4B9CE701519A4463010844671F9B@bgsmsx502.gar.corp.intel.com>
On Thu, Jan 13, 2011 at 05:06:19PM +0530, Koul, Vinod wrote:
> Yes on both of these, but I didn't want to break current method.
> So I kept these to ensure both methods work fine.
> One we have converted all driver to use register then we can remove these.
> Would have made sense to put a comment for that
My plan for this when I originally wrote the comment had been to make
the contents of the soc-audio device probe and removal look exactly like
what you'd write directly in a machine driver so no code except for the
code doing the soc-audio device had any idea it was there. This would
keep backwards compatiblity without special casing, making things more
maintainable.
next prev parent reply other threads:[~2011-01-13 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 6:49 [PATCH] ASoC: Make register_card API available to drivers Koul, Vinod
2011-01-13 11:26 ` Mark Brown
2011-01-13 11:36 ` Koul, Vinod
2011-01-13 11:42 ` Mark Brown [this message]
2011-01-13 13:24 ` Koul, Vinod
2011-01-13 13:34 ` Mark Brown
2011-01-13 14:01 ` Koul, Vinod
2011-01-13 15:08 ` Mark Brown
2011-01-13 17:13 ` Koul, Vinod
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=20110113114203.GA30351@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=priya.harsha@intel.com \
--cc=selma.bensaid@intel.com \
--cc=vinod.koul@intel.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 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.