From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] MOP500 Audio patches due for ASoC
Date: Fri, 28 Sep 2012 13:37:43 +0100 [thread overview]
Message-ID: <20120928123743.GE30869@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120927150119.GD1176@gmail.com>
On Thu, Sep 27, 2012 at 04:01:19PM +0100, Lee Jones wrote:
> Is there any reason why the following patches didn't make it into -next?
> ASoC: codecs: Enable AB8500 CODEC for Device Tree
> ASoC: Ux500: Enable ux500 MSP driver for Device Tree
They appear to be there, there's certainly no reason why they'd be any
different to the rest of the series.
next prev parent reply other threads:[~2012-09-28 12:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 12:09 [GIT PULL] MOP500 Audio patches due for ASoC Lee Jones
2012-09-20 12:09 ` [PATCH 1/7] ASoC: Ux500: Move MSP pinctrl setup into the MSP driver Lee Jones
2012-09-20 12:09 ` [PATCH 2/7] ASoC: Ux500: Enable MOP500 driver for Device Tree Lee Jones
2012-09-20 12:09 ` [PATCH 3/7] ASoC: Ux500: Enable ux500 MSP " Lee Jones
2012-09-20 12:09 ` [PATCH 4/7] ASoC: codecs: Enable AB8500 CODEC " Lee Jones
2012-09-20 12:09 ` [PATCH 5/7] ASoC: Ux500: Minor coding layout changes Lee Jones
2012-09-20 12:09 ` [PATCH 6/7] Documentation: Define the MOP500 Audio Machine Driver Device Tree bindings Lee Jones
2012-09-20 12:09 ` [PATCH 7/7] Documentation: Define the MSP " Lee Jones
2012-09-20 12:56 ` [GIT PULL] MOP500 Audio patches due for ASoC Mark Brown
2012-09-20 13:06 ` Lee Jones
2012-09-27 15:01 ` Lee Jones
2012-09-28 12:37 ` Mark Brown [this message]
2012-09-28 14:59 ` Lee Jones
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=20120928123743.GE30869@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).