From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 0/7] Wolfson MFD updates
Date: Fri, 26 Nov 2010 14:07:19 +0000 [thread overview]
Message-ID: <20101126140719.GH30360@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20101126140518.GN5520@sortiz-mobl>
On Fri, Nov 26, 2010 at 03:05:19PM +0100, Samuel Ortiz wrote:
> On Wed, Nov 24, 2010 at 06:00:55PM +0000, Mark Brown wrote:
> > This is a reposting of a number of Wolfson MFD patches previously posted
> > - I seem to building up a relatively large queue of patches here.
> > Patch 1/7 is a bugfix and really ought to go into 2.6.37, patch 7/7
> > would ideally be merged via ASoC as the bulk of the support for this
> > device is in the CODEC driver, 2-3 are a new device and 4-6 are some
> > housekeeping for new kernel APIs.
> All 7 patches applied, thanks a lot.
Thanks!
Would it be OK to apply patch 7 to the ASoC tree? There's a bunch of
CODEC driver changes to support the WM8958 which depend on it and also
depend on changes in the ASoC tree.
next prev parent reply other threads:[~2010-11-26 14:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 18:00 [PATCH 0/7] Wolfson MFD updates Mark Brown
2010-11-24 18:01 ` [PATCH 2.6.37 1/7] mfd: Supply IRQ base for WM832x devices Mark Brown
2010-11-24 18:01 ` [PATCH 2/7] mfd: Simplify WM832x subdevice instantiation Mark Brown
2010-11-24 18:01 ` [PATCH 3/7] mfd: Add WM8326 support Mark Brown
2010-11-24 18:01 ` [PATCH 4/7] mfd: Convert WM831x to new irq_ interrupt methods Mark Brown
2010-11-24 18:01 ` [PATCH 5/7] mfd: Convert WM835x " Mark Brown
2010-11-24 18:01 ` [PATCH 6/7] mfd: Convert WM8994 " Mark Brown
2010-11-24 18:01 ` [PATCH 7/7] mfd: Add initial WM8958 support Mark Brown
2010-11-26 14:05 ` [PATCH 0/7] Wolfson MFD updates Samuel Ortiz
2010-11-26 14:07 ` Mark Brown [this message]
2010-11-26 14:51 ` Samuel Ortiz
2010-11-26 15:18 ` 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=20101126140719.GH30360@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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