From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: alsa-devel@alsa-project.org, saeed@marvell.com,
apatard@mandriva.com, tbm@cyrius.com,
linux-arm-kernel@lists.infradead.org, lrg@slimlogic.co.uk
Subject: Re: [patch 0/5] kirkwood openrd client audio support - v3
Date: Tue, 25 May 2010 19:31:54 -0700 [thread overview]
Message-ID: <20100526023153.GA15249@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1005251925010.24526@xanadu.home>
On Tue, May 25, 2010 at 09:10:54PM -0400, Nicolas Pitre wrote:
> I don't mind if you wish to carry it through the ASOC tree. The bulk of
> it is ASOC related anyway. However I think that "orion" names should be
> "kirkwood" throughout instead, as pure Orion chips have no audio
> interfaces.
Can I add an ack from you for the patches with the name change, then?
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 0/5] kirkwood openrd client audio support - v3
Date: Tue, 25 May 2010 19:31:54 -0700 [thread overview]
Message-ID: <20100526023153.GA15249@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1005251925010.24526@xanadu.home>
On Tue, May 25, 2010 at 09:10:54PM -0400, Nicolas Pitre wrote:
> I don't mind if you wish to carry it through the ASOC tree. The bulk of
> it is ASOC related anyway. However I think that "orion" names should be
> "kirkwood" throughout instead, as pure Orion chips have no audio
> interfaces.
Can I add an ack from you for the patches with the name change, then?
next prev parent reply other threads:[~2010-05-26 2:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 12:22 [patch 0/5] kirkwood openrd client audio support - v3 apatard
2010-05-25 12:22 ` apatard at mandriva.com
2010-05-25 12:22 ` [patch 1/5] orion/kirkwood: add audio functions apatard
2010-05-25 12:22 ` apatard at mandriva.com
2010-05-25 12:22 ` [patch 2/5] openrd-client: initialise audio apatard
2010-05-25 12:22 ` apatard at mandriva.com
2010-05-25 12:22 ` [patch 3/5] cs42l51: add asoc driver apatard
2010-05-25 12:22 ` apatard at mandriva.com
2010-05-25 22:51 ` Mark Brown
2010-05-25 22:51 ` Mark Brown
2010-05-26 8:20 ` Arnaud Patard
2010-05-26 8:20 ` Arnaud Patard
2010-05-27 0:52 ` Mark Brown
2010-05-27 0:52 ` [alsa-devel] " Mark Brown
2010-05-25 12:22 ` [patch 4/5] orion/kirkwood: Add i2s support apatard
2010-05-25 12:22 ` apatard at mandriva.com
2010-05-26 0:31 ` Nicolas Pitre
2010-05-26 0:31 ` Nicolas Pitre
2010-05-26 5:15 ` saeed bishara
2010-05-26 5:15 ` saeed bishara
2010-05-26 16:55 ` Nicolas Pitre
2010-05-26 16:55 ` Nicolas Pitre
2010-05-26 8:25 ` Arnaud Patard
2010-05-26 8:25 ` Arnaud Patard
2010-05-26 17:02 ` Nicolas Pitre
2010-05-26 17:02 ` Nicolas Pitre
2010-05-25 12:22 ` [patch 5/5] kirkwood: Add audio support to openrd client platforms apatard
2010-05-25 12:22 ` apatard at mandriva.com
2010-05-25 23:18 ` [patch 0/5] kirkwood openrd client audio support - v3 Mark Brown
2010-05-25 23:18 ` Mark Brown
2010-05-26 1:10 ` Nicolas Pitre
2010-05-26 1:10 ` Nicolas Pitre
2010-05-26 2:31 ` Mark Brown [this message]
2010-05-26 2:31 ` Mark Brown
2010-05-26 2:49 ` Nicolas Pitre
2010-05-26 2:49 ` Nicolas Pitre
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=20100526023153.GA15249@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=apatard@mandriva.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lrg@slimlogic.co.uk \
--cc=nico@fluxnic.net \
--cc=saeed@marvell.com \
--cc=tbm@cyrius.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 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.