From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Geoffrey Wossum <geoffrey@pager.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC Platform Driver for AT32AP7000 (AVR32)
Date: Wed, 28 May 2008 16:40:00 +0100 [thread overview]
Message-ID: <20080528153958.GE12414@sirena.org.uk> (raw)
In-Reply-To: <200805281028.59582.geoffrey@pager.net>
On Wed, May 28, 2008 at 10:28:59AM -0500, Geoffrey Wossum wrote:
> Do I need to submit patches to fix the style issues?
Ideally, yes; there are some not entirely mechanical things in there as
well so it'd be good to make sure that what goes in has been tested
as-is.
> > Will this driver work with a current mainline kernel or does it require
> > other things from the Atmel kernel?
> at32-pcm.c and at32-ssc.c will compile against a vanilla 2.6.24.3 kernel.
> playpaq_wm8510.c will not, since it references the WM8510 code that is not in
> the mainline kernel. Not sure if it would really work. Even though AVR32 is
We should be able to submit the WM8510 driver so it shouldn't be a
blocker.
> in the mainline kernel, Atmel still has a fairly extensive patch against the
> kernel. Until you can use an unpatched and current kernel for the AVR32,
> this code probably isn't a candidate for inclusion the mainline.
OTOH, if it will build with current mainline then that reduces the diff
that one needs to carry in order to use this support and means there's
one less thing in that diff that needs to be merged into mainline. That
seems like a net win to me.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
prev parent reply other threads:[~2008-05-28 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 22:32 [PATCH] ASoC Platform Driver for AT32AP7000 (AVR32) Geoffrey Wossum
2008-05-28 11:18 ` Mark Brown
2008-05-28 15:28 ` Geoffrey Wossum
2008-05-28 15:40 ` Mark Brown [this message]
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=20080528153958.GE12414@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=geoffrey@pager.net \
/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