From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Philippe Rétornaz" <philippe.retornaz@epfl.ch>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
J?rgen Lambrecht <juergen.lambrecht@gmail.com>,
Lambrecht J?rgen <J.Lambrecht@televic.com>,
Fabio Estevam <festevam@gmail.com>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH] ARM ASoC: add sound driver for imx27pdk using mc13783 codec
Date: Fri, 3 Feb 2012 11:58:06 +0000 [thread overview]
Message-ID: <20120203115806.GI3151@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1635894.OLo8mNMWim@laptop>
[-- Attachment #1.1: Type: text/plain, Size: 435 bytes --]
On Fri, Feb 03, 2012 at 08:45:10AM +0100, Philippe Rétornaz wrote:
> Le jeudi 2 février 2012 17:32:12 Mark Brown a écrit :
> > First step would be to post it :)
> Well, that was the whole point to post a link to a git tree containing the
> patches. But if you think I should post the patches directly on the mailing
> list I can do it.
The entire kernel code review process is based on patches posted to
mailing lists.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [RFC PATCH] ARM ASoC: add sound driver for imx27pdk using mc13783 codec
Date: Fri, 3 Feb 2012 11:58:06 +0000 [thread overview]
Message-ID: <20120203115806.GI3151@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1635894.OLo8mNMWim@laptop>
On Fri, Feb 03, 2012 at 08:45:10AM +0100, Philippe R?tornaz wrote:
> Le jeudi 2 f?vrier 2012 17:32:12 Mark Brown a ?crit :
> > First step would be to post it :)
> Well, that was the whole point to post a link to a git tree containing the
> patches. But if you think I should post the patches directly on the mailing
> list I can do it.
The entire kernel code review process is based on patches posted to
mailing lists.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120203/9a52f826/attachment-0001.sig>
next prev parent reply other threads:[~2012-02-03 11:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 13:24 [RFC PATCH] ARM ASoC: add sound driver for imx27pdk using mc13783 codec Jürgen Lambrecht
2011-07-08 13:24 ` Jürgen Lambrecht
2011-07-08 14:11 ` Philippe Rétornaz
2011-07-08 14:11 ` Philippe Rétornaz
2011-07-08 14:19 ` Lambrecht Jürgen
2011-07-08 14:19 ` Lambrecht Jürgen
2011-07-27 8:28 ` Philippe Rétornaz
2011-07-27 8:28 ` Philippe Rétornaz
2011-07-29 19:14 ` Jürgen Lambrecht
2011-07-29 19:14 ` Jürgen Lambrecht
2011-09-20 11:39 ` Philippe Rétornaz
2011-09-20 11:39 ` Philippe Rétornaz
2012-01-25 15:45 ` Philippe Rétornaz
2012-01-25 15:45 ` Philippe Rétornaz
2012-01-28 20:57 ` Fabio Estevam
2012-01-28 20:57 ` Fabio Estevam
2012-01-29 19:01 ` Philippe Rétornaz
2012-01-29 19:01 ` Philippe Rétornaz
2012-01-30 15:59 ` Fabio Estevam
2012-01-30 15:59 ` Fabio Estevam
2012-02-02 17:32 ` Mark Brown
2012-02-02 17:32 ` [alsa-devel] " Mark Brown
2012-02-03 7:45 ` Philippe Rétornaz
2012-02-03 7:45 ` [alsa-devel] " Philippe Rétornaz
2012-02-03 11:58 ` Mark Brown [this message]
2012-02-03 11:58 ` Mark Brown
2012-02-09 21:24 ` Fabio Estevam
2012-02-09 21:24 ` [alsa-devel] " Fabio Estevam
2011-07-09 2:25 ` Mark Brown
2011-07-09 2:25 ` Mark Brown
2011-07-11 10:30 ` Lambrecht Jürgen
2011-07-11 10:30 ` Lambrecht Jürgen
2011-07-11 11:44 ` Mark Brown
2011-07-11 11:44 ` 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=20120203115806.GI3151@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=J.Lambrecht@televic.com \
--cc=alsa-devel@alsa-project.org \
--cc=festevam@gmail.com \
--cc=juergen.lambrecht@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=philippe.retornaz@epfl.ch \
--cc=s.hauer@pengutronix.de \
/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.