From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: alsa-devel@alsa-project.org, eric.y.miao@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] WM8750: Fix SPITZ machine
Date: Thu, 8 Apr 2010 10:40:40 +0100 [thread overview]
Message-ID: <20100408094040.GA6303@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <201004072250.22351.marek.vasut@gmail.com>
On Wed, Apr 07, 2010 at 10:50:22PM +0200, Marek Vasut wrote:
> Dne Po 5. dubna 2010 15:41:07 Mark Brown napsal(a):
> > As I've mentioned several times before I urge you to look at how this
> > transition was done for wm8731 for an example of how this sort of change
> > can be done without too much disruption.
> Can you possibly elaborate ? I was unable to find it.
Commit 5998102b9095fdb7c67755812038612afea315c5 upstream:
http://git.kernel.org/?p=linux/kernel/git/broonie/sound-2.6.git;a=commit;h=5998102b9095fdb7c67755812038612afea315c5
Notice how this updates both the machines and the CODEC in the same
patch so things always compile and run.
next prev parent reply other threads:[~2010-04-08 9:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 4:00 [PATCH 1/3] WM8750: Convert to new API Marek Vasut
2010-04-05 4:00 ` [PATCH 2/3] WM8750: Fix SPITZ machine Marek Vasut
2010-04-05 4:00 ` [PATCH 3/3] Zipit Z2 WM8750 aSoC driver Marek Vasut
2010-04-05 4:10 ` [PATCH 1/3] WM8750: Convert to new API Marek Vasut
2010-04-05 4:13 ` Marek Vasut
2010-04-05 13:44 ` Mark Brown
2010-04-05 4:13 ` [PATCH 2/3] WM8750: Fix SPITZ machine Marek Vasut
2010-04-05 13:41 ` Mark Brown
2010-04-07 20:50 ` Marek Vasut
2010-04-08 9:40 ` Mark Brown [this message]
2010-04-08 14:51 ` [PATCH] WM8750: Convert to new API Marek Vasut
2010-04-08 14:58 ` Mark Brown
2010-04-05 4:13 ` [PATCH 3/3] Zipit Z2 WM8750 aSoC driver Marek Vasut
2010-04-05 13:42 ` Mark Brown
2010-04-05 14:12 ` Liam Girdwood
2010-04-09 21:48 ` Marek Vasut
2010-04-12 10:37 ` Mark Brown
2010-04-12 12:34 ` Marek Vasut
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=20100408094040.GA6303@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marek.vasut@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;
as well as URLs for NNTP newsgroup(s).