From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Robin Getz <rgetz@blackfin.uclinux.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mike Frysinger <vapier.adi@gmail.com>,
Barry Song <21cnbao@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [alsa-devel] [PATCH] New ASoC Drivers for ADI AD1938 codec
Date: Sun, 21 Jun 2009 01:13:39 +0100 [thread overview]
Message-ID: <982CEEB9-22E6-4CE6-833F-806D31E8D6B8@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <200906201915.39935.rgetz@blackfin.uclinux.org> (sfid-20090621_001240_652537_BCBB3B6E)
On 21 Jun 2009, at 00:15, Robin Getz <rgetz@blackfin.uclinux.org> wrote:
> Any reason why platform/board specific things are in sound/soc/arch
> rather
>>>
>>
> than arch/xxxx/boards - like the majority of drivers?
Partly because the APIs are sufficiently fluid to make the cross tree
merge issues unmanageable, partly because non trivial boards really do
need an entire driver for the board. I'd also say that at the minute
I'm catching enough errors on review of machine drivers to make it
worthwhile.
>
next prev parent reply other threads:[~2009-06-21 0:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 9:28 Barry Song
2009-06-19 9:35 ` Liam Girdwood
2009-06-19 9:41 ` Liam Girdwood
2009-06-19 10:47 ` Mark Brown
2009-06-19 11:05 ` Mike Frysinger
2009-06-19 11:13 ` Mark Brown
2009-06-19 11:21 ` Mike Frysinger
2009-06-19 11:56 ` Mark Brown
2009-06-20 23:15 ` [alsa-devel] " Robin Getz
2009-06-21 0:13 ` Mark Brown [this message]
[not found] ` <3c17e3570906212008n6071e987sbcd4b9377364ae78@mail.gmail.com>
2009-06-22 10:57 ` Mark Brown
[not found] ` <3c17e3570906220600l3471b6f0rc29c674b4a5ec2df@mail.gmail.com>
2009-06-22 13:11 ` Mark Brown
2009-07-13 8:12 ` 宋宝华
2009-07-13 9:15 ` 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=982CEEB9-22E6-4CE6-833F-806D31E8D6B8@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=21cnbao@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=rgetz@blackfin.uclinux.org \
--cc=vapier.adi@gmail.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
all inboxes | Powered by JetHome®