From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Peter Ujfalusi <peter.ujfalusi@nokia.com>,
tony@atomide.com, alsa-devel@alsa-project.org,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH 1/4 v2] MFD: twl4030: add twl4030_codec MFD as a new child to the core
Date: Sun, 25 Oct 2009 17:18:39 +0000 [thread overview]
Message-ID: <20091025171838.GA5141@sirena.org.uk> (raw)
In-Reply-To: <20091023140703.GA3718@sortiz.org>
On Fri, Oct 23, 2009 at 04:07:05PM +0200, Samuel Ortiz wrote:
> As agreed, Mark is taking this one. So:
> Acked-by: Samuel Ortiz <sameo@linux.intel.com>
Applied all, if there's a merge problem with the MFD code then there's a
twl4030-mfd branch at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git
which I'm happy for you to merge if it makes life easier. Due to other
changes the patches end up depending on (just textually I think) there's
a big raft of other stuff in there too, sadly.
prev parent reply other threads:[~2009-10-25 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 10:26 [PATCH 0/4 v2] MFD/OMAP/ASoC: MFD device for twl4030 codec submodule Peter Ujfalusi
2009-10-22 10:26 ` [PATCH 1/4 v2] MFD: twl4030: add twl4030_codec MFD as a new child to the core Peter Ujfalusi
2009-10-22 10:26 ` [PATCH 2/4 v2] OMAP: Platform support for twl4030_codec MFD Peter Ujfalusi
2009-10-22 10:26 ` [PATCH 3/4 v2] ASoC: TWL4030: use the twl4030-codec.h for register descriptions Peter Ujfalusi
2009-10-22 10:26 ` [PATCH 4/4 v2] ASoC: TWL4030: Driver registration via twl4030_codec MFD Peter Ujfalusi
2009-10-22 16:56 ` Mark Brown
2009-10-23 5:27 ` Peter Ujfalusi
2009-10-23 12:59 ` [alsa-devel] " Mark Brown
2009-10-23 14:07 ` [PATCH 1/4 v2] MFD: twl4030: add twl4030_codec MFD as a new child to the core Samuel Ortiz
2009-10-25 17:18 ` 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=20091025171838.GA5141@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@nokia.com \
--cc=sameo@linux.intel.com \
--cc=tony@atomide.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®