From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Mike Frysinger <vapier@gentoo.org>,
Sonic Zhang <sonic.zhang@analog.com>,
Barry Song <21cnbao@gmail.com>, Cliff Cai <cliff.cai@analog.com>
Cc: uclinux-dist-devel@blackfin.uclinux.org,
alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Blackfin ASoC drivers with multi-component
Date: Sun, 28 Nov 2010 12:35:58 +0000 [thread overview]
Message-ID: <20101128123558.GB12683@opensource.wolfsonmicro.com> (raw)
I'm a little concerned that there have been no updates to the Blackfin
audio drivers since the merge of multi-component ASoC (which is now in
mainline and should be released as part of 2.6.37). This was a very
big and invasive update, and experience with other architectures has
been that there's usually at least some typos that need fixing. It'd be
good to get some confirmation that the audio drivers have at least been
tested with current mainline - if everything worked fine that's
obviously excellent but it'd be good if someone could confirm that this
is the case.
There was some discussion with Mike at the time the drivers were merged
but it sounded more like "I need to get the audio guys to look at this"
than a report of actual testing and there's been nothing since.
next reply other threads:[~2010-11-28 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 12:35 Mark Brown [this message]
2010-11-29 1:16 ` Blackfin ASoC drivers with multi-component Cai, Cliff
[not found] ` <20101128123558.GB12683-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2010-11-29 2:27 ` Zhang, Sonic
2010-11-29 10:56 ` 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=20101128123558.GB12683@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=21cnbao@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=cliff.cai@analog.com \
--cc=lrg@slimlogic.co.uk \
--cc=sonic.zhang@analog.com \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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 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.