From: jassi brar <jassisinghbrar@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, ben-linux@fluff.org,
Jassi Brar <jassi.brar@samsung.com>
Subject: Re: Reforming S3C I2S towards supporting I2Sv4
Date: Tue, 27 Apr 2010 11:10:34 +0900 [thread overview]
Message-ID: <k2q1b68c6791004261910i5477363dyc01af4d85f8d55b@mail.gmail.com> (raw)
In-Reply-To: <h2m1b68c6791004051733s67d23167s588fa3e8c59e9958@mail.gmail.com>
On Tue, Apr 6, 2010 at 9:33 AM, jassi brar <jassisinghbrar@gmail.com> wrote:
> On Wed, Mar 10, 2010 at 11:23 PM, Mark Brown
> <broonie@opensource.wolfsonmicro.com> wrote:
>> On Wed, Mar 10, 2010 at 04:48:55PM +0900, Jassi Brar wrote:
>>
>>> I have prepared some patches that debug and modify the behaviour of
>>> extant S3C I2S support towards managing I2Sv4 controllers as well.
>>
>> OK, I think that's everything. I've not applied anything after the
>> header move yet due to the need for an ack from Ben.
> Hi Ben,
>
> Could you please comment ? If need be I can resend the patches.
ping
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2010-04-27 2:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 7:48 Reforming S3C I2S towards supporting I2Sv4 Jassi Brar
2010-03-10 8:24 ` Liam Girdwood
2010-03-10 8:31 ` jassi brar
2010-03-10 9:04 ` Liam Girdwood
2010-03-10 9:22 ` jassi brar
2010-03-10 10:18 ` Mark Brown
2010-03-10 8:35 ` jassi brar
2010-03-10 8:51 ` Liam Girdwood
2010-03-10 9:02 ` jassi brar
2010-03-10 10:20 ` Mark Brown
2010-03-10 14:23 ` Mark Brown
2010-04-06 0:33 ` jassi brar
2010-04-27 2:10 ` jassi brar [this message]
2010-04-27 2:58 ` Ben Dooks
2010-04-27 4:25 ` jassi brar
2010-05-02 4:38 ` Kyungmin Park
2010-05-02 8:28 ` jassi brar
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=k2q1b68c6791004261910i5477363dyc01af4d85f8d55b@mail.gmail.com \
--to=jassisinghbrar@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jassi.brar@samsung.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).