From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
sandeep@freescale.com, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [2/3][PATCH][v2] TDM Framework
Date: Mon, 30 Jul 2012 16:45:36 +0100 [thread overview]
Message-ID: <20120730154536.GA3218@sirena.org.uk> (raw)
In-Reply-To: <20120727152542.GB1613@electric-eye.fr.zoreil.com>
On Fri, Jul 27, 2012 at 05:25:42PM +0200, Francois Romieu wrote:
> 2. It would probably make sense to Cc: netdev and serial. There may be
> some kernel client network integration from the start.
Plus audio, quite a few of the buses mentioned as examples of use cases
for the hardware are audio ones.
next prev parent reply other threads:[~2012-07-30 16:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 14:05 [2/3][PATCH][v2] TDM Framework sandeep
2012-07-27 14:05 ` [1/3][PATCH][v2] Adding documentation for TDM sandeep
2012-07-27 14:05 ` [3/3][PATCH][v2] Added TDM device support and Freescale Starlite driver sandeep
2012-07-27 14:11 ` [2/3][PATCH][v2] TDM Framework John Stoffel
2012-07-30 9:29 ` Singh Sandeep-B37400
2012-07-30 14:10 ` John Stoffel
2012-07-31 6:40 ` Singh Sandeep-B37400
2012-07-27 14:51 ` Russell King - ARM Linux
2012-07-30 13:00 ` Singh Sandeep-B37400
2012-07-27 15:25 ` Francois Romieu
2012-07-30 9:50 ` Singh Sandeep-B37400
2012-07-30 16:01 ` Greg KH
2012-08-01 12:13 ` Singh Sandeep-B37400
2012-08-01 12:37 ` Greg KH
2012-08-21 14:13 ` Mark Brown
2012-07-30 15:45 ` Mark Brown [this message]
2012-07-31 6:41 ` Singh Sandeep-B37400
2012-07-27 17:59 ` Greg KH
2012-07-30 9:10 ` Aggrwal Poonam-B10812
2012-07-30 16:04 ` Greg KH
2012-07-27 18:12 ` Greg KH
2012-07-30 9:13 ` Aggrwal Poonam-B10812
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=20120730154536.GA3218@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=romieu@fr.zoreil.com \
--cc=sandeep@freescale.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).