From: Mark Brown <broonie@kernel.org>
To: Barry Song <21cnbao@gmail.com>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
lgirdwood@gmail.com, workgroup.linux@csr.com,
Graeme Gregory <graeme@openmoko.org>,
Barry Song <Baohua.Song@csr.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: dfbmcs320: make the driver common for other BT modules
Date: Thu, 16 May 2013 18:35:59 +0100 [thread overview]
Message-ID: <20130516173559.GD1627@sirena.org.uk> (raw)
In-Reply-To: <CAGsJ_4yn2uodRKrFKYrX85XA7A=hQs2w0cyGoEEHsYgCJHD7eQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 552 bytes --]
On Thu, May 16, 2013 at 08:00:17PM +0800, Barry Song wrote:
> i did think it is a good idea to have device id list while i sent the
> last mail. and it matches with the generic device driver engineering
> sense. the problem is i don't how long the list will be.
> if you like to keep dfbmcs320 at least for the moment, i would agree.
I'd prefer to see the ID list; we shouldn't be throwing away
information. Probably we can go a long way towards cutting down the
length of the list if it gets silly with use of wildcards in the device
names listed.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH] ASoC: dfbmcs320: make the driver common for other BT modules
Date: Thu, 16 May 2013 18:35:59 +0100 [thread overview]
Message-ID: <20130516173559.GD1627@sirena.org.uk> (raw)
In-Reply-To: <CAGsJ_4yn2uodRKrFKYrX85XA7A=hQs2w0cyGoEEHsYgCJHD7eQ@mail.gmail.com>
On Thu, May 16, 2013 at 08:00:17PM +0800, Barry Song wrote:
> i did think it is a good idea to have device id list while i sent the
> last mail. and it matches with the generic device driver engineering
> sense. the problem is i don't how long the list will be.
> if you like to keep dfbmcs320 at least for the moment, i would agree.
I'd prefer to see the ID list; we shouldn't be throwing away
information. Probably we can go a long way towards cutting down the
length of the list if it gets silly with use of wildcards in the device
names listed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130516/b49bd1d4/attachment.sig>
next prev parent reply other threads:[~2013-05-16 17:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 6:53 [PATCH] ASoC: dfbmcs320: make the driver common for other BT modules Barry Song
2013-05-16 6:53 ` Barry Song
2013-05-16 9:51 ` Lars-Peter Clausen
2013-05-16 9:51 ` Lars-Peter Clausen
2013-05-16 10:31 ` Barry Song
2013-05-16 10:31 ` [alsa-devel] " Barry Song
2013-05-16 11:29 ` Lars-Peter Clausen
2013-05-16 11:29 ` [alsa-devel] " Lars-Peter Clausen
2013-05-16 12:00 ` Barry Song
2013-05-16 12:00 ` [alsa-devel] " Barry Song
2013-05-16 17:35 ` Mark Brown [this message]
2013-05-16 17:35 ` 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=20130516173559.GD1627@sirena.org.uk \
--to=broonie@kernel.org \
--cc=21cnbao@gmail.com \
--cc=Baohua.Song@csr.com \
--cc=alsa-devel@alsa-project.org \
--cc=graeme@openmoko.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=workgroup.linux@csr.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.