From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Daniel Glöckner" <dg@emlix.com>
Cc: Chris Zankel <chris@zankel.net>,
alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: S6000 ASoC drivers with multi-component
Date: Mon, 29 Nov 2010 10:42:29 +0000 [thread overview]
Message-ID: <20101129104228.GM30360@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <4CF3819B.5040507@emlix.com>
On Mon, Nov 29, 2010 at 11:34:03AM +0100, Daniel Glöckner wrote:
> But trying to build a s6105 kernel from vanilla sources made me realize
> two things:
> 1. Nobody ever tried to do that before as s6000 support has been merged
> incompletely and in some cases with merge errors (variant_irq_disable
> declaration, I2C_BOARD_INFO in struct platform_device[], clk framework
> missing completely).
Actually, Liam did try and fail when he was testing the changes.
> So for now I could just compile-test the ASoC changes. Actually booting a
> kernel will probably take more of my spare time..
> Would you like to have patches for the found ASoC bugs now or do you prefer
> waiting until I could make it work on hardware?
Just send stuff as you find it, no problem sending multiple patches and
it's less diff to carry.
next prev parent reply other threads:[~2010-11-29 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 12:07 S6000 ASoC drivers with multi-component Mark Brown
2010-11-29 10:34 ` Daniel Glöckner
2010-11-29 10:42 ` Mark Brown [this message]
2010-11-30 0:00 ` [PATCH 1/3] s6000-i2s: fix compilation Daniel Glöckner
2010-11-30 11:21 ` Liam Girdwood
2010-11-30 11:26 ` Mark Brown
2010-11-30 0:00 ` [PATCH 2/3] s6000-pcm: " Daniel Glöckner
2010-11-30 0:00 ` [PATCH 3/3] s6105-ipcam: " Daniel Glöckner
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=20101129104228.GM30360@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=chris@zankel.net \
--cc=dg@emlix.com \
--cc=lrg@slimlogic.co.uk \
/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.