From: Ryan Mallon <ryan@bluewatersys.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>
Cc: "john.cooper@third-harmonic.com" <john.cooper@third-harmonic.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"chasedouglas@gmail.com" <chasedouglas@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"r&d4@dave-tech.it" <r&d4@dave-tech.it>,
"dhuggins@cs.cmu.edu" <dhuggins@cs.cmu.edu>,
"marshall@coolbananas.co.nz" <marshall@coolbananas.co.nz>,
"buytenh@wantstofly.org" <buytenh@wantstofly.org>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/3] EP93xx: Add i2s core support
Date: Wed, 09 Jun 2010 07:27:03 +1200 [thread overview]
Message-ID: <4C0E9987.2010907@bluewatersys.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B027084269763708AFD76@AUSP01VMBX24.collaborationhost.net>
H Hartley Sweeten wrote:
> On Tuesday, June 08, 2010 3:01 AM, Ryan Mallon wrote:
>> Add core support for EP93xx i2s audio
>>
>> Signed-off-by: Ryan Mallon <ryan@bluewatersys.com>
>
> Looks good.
>
> Acked-by: H Hartley Sweeten <hsweeten@visionengravers.com>
>
Okay, I have Liam and Hartley's acks on this one and Liam's on 3/3.
Mark, do you want to apply the other two patches to your tree, or should
they go via the arm tree?
Thanks,
~Ryan
WARNING: multiple messages have this Message-ID (diff)
From: ryan@bluewatersys.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] EP93xx: Add i2s core support
Date: Wed, 09 Jun 2010 07:27:03 +1200 [thread overview]
Message-ID: <4C0E9987.2010907@bluewatersys.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B027084269763708AFD76@AUSP01VMBX24.collaborationhost.net>
H Hartley Sweeten wrote:
> On Tuesday, June 08, 2010 3:01 AM, Ryan Mallon wrote:
>> Add core support for EP93xx i2s audio
>>
>> Signed-off-by: Ryan Mallon <ryan@bluewatersys.com>
>
> Looks good.
>
> Acked-by: H Hartley Sweeten <hsweeten@visionengravers.com>
>
Okay, I have Liam and Hartley's acks on this one and Liam's on 3/3.
Mark, do you want to apply the other two patches to your tree, or should
they go via the arm tree?
Thanks,
~Ryan
next prev parent reply other threads:[~2010-06-08 19:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 10:01 [PATCH 0/3] EP93xx: Add i2s audio support Ryan Mallon
2010-06-08 10:01 ` Ryan Mallon
2010-06-08 10:01 ` [PATCH 1/3] EP93xx: Add i2s core support Ryan Mallon
2010-06-08 10:01 ` Ryan Mallon
2010-06-08 15:01 ` H Hartley Sweeten
2010-06-08 15:01 ` H Hartley Sweeten
2010-06-08 19:27 ` Ryan Mallon [this message]
2010-06-08 19:27 ` Ryan Mallon
2010-06-08 23:21 ` Mark Brown
2010-06-08 23:21 ` Mark Brown
2010-06-08 23:26 ` Ryan Mallon
2010-06-08 23:26 ` Ryan Mallon
2010-06-08 23:29 ` Mark Brown
2010-06-08 23:29 ` Mark Brown
2010-06-08 23:32 ` Ryan Mallon
2010-06-08 23:32 ` Ryan Mallon
2010-06-08 23:26 ` H Hartley Sweeten
2010-06-08 23:26 ` H Hartley Sweeten
2010-06-08 10:01 ` [PATCH 2/3] EP93xx: Add i2s audio driver Ryan Mallon
2010-06-08 10:01 ` Ryan Mallon
2010-06-08 10:05 ` Mark Brown
2010-06-08 10:05 ` Mark Brown
2010-06-08 10:09 ` Ryan Mallon
2010-06-08 10:09 ` [alsa-devel] " Ryan Mallon
2010-06-08 10:24 ` Mark Brown
2010-06-08 10:24 ` [alsa-devel] " Mark Brown
2010-06-08 10:01 ` [PATCH 3/3] EP93xx: Add Snapper CL15 i2s audio support Ryan Mallon
2010-06-08 10:01 ` Ryan Mallon
2010-06-09 10:17 ` [PATCH 0/3] EP93xx: Add " Mark Brown
2010-06-09 10:17 ` Mark Brown
2010-06-09 21:40 ` Ryan Mallon
2010-06-09 21:40 ` Ryan Mallon
2010-06-09 22:22 ` Mark Brown
2010-06-09 22:22 ` Mark Brown
2010-06-10 20:46 ` Ryan Mallon
2010-06-10 20:46 ` Ryan Mallon
2010-06-11 9:35 ` Mark Brown
2010-06-11 9:35 ` [alsa-devel] " 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=4C0E9987.2010907@bluewatersys.com \
--to=ryan@bluewatersys.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=buytenh@wantstofly.org \
--cc=chasedouglas@gmail.com \
--cc=dhuggins@cs.cmu.edu \
--cc=hartleys@visionengravers.com \
--cc=john.cooper@third-harmonic.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lrg@slimlogic.co.uk \
--cc=marshall@coolbananas.co.nz \
--cc=r&d4@dave-tech.it \
/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.