From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Padma Venkat <padma.kvr@gmail.com>
Cc: Padmavathi Venna <padma.v@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, alsa-devel@alsa-project.org,
devicetree-discuss@lists.ozlabs.org, sbkim73@samsung.com,
ben-linux@fluff.org, kgene.kim@samsung.com
Subject: Re: [RFC PATCH] ASoC: Samsung: Register the audio platform device
Date: Mon, 26 Nov 2012 14:49:44 +0000 [thread overview]
Message-ID: <20121126144943.GM9411@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAAgF-BdHm_VFB-xsZ6kpAu5+9+1yMNVVGM_og+H3QghWQuf8+w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
On Mon, Nov 26, 2012 at 08:15:12PM +0530, Padma Venkat wrote:
> On Wed, Nov 14, 2012 at 5:39 PM, Padmavathi Venna <padma.v@samsung.com> wrote:
> > +module_init(smdk_audio_init);
> > +module_exit(smdk_audio_exit);
> Ping. Any comments on this patch?
Don't send contentless pings and delete irrelevant context from replies.
Please refer to the feedback I sent in response to Sangbeom's pull
request - in short, this isn't the way to do this - do what the other
platforms do.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ASoC: Samsung: Register the audio platform device
Date: Mon, 26 Nov 2012 14:49:44 +0000 [thread overview]
Message-ID: <20121126144943.GM9411@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAAgF-BdHm_VFB-xsZ6kpAu5+9+1yMNVVGM_og+H3QghWQuf8+w@mail.gmail.com>
On Mon, Nov 26, 2012 at 08:15:12PM +0530, Padma Venkat wrote:
> On Wed, Nov 14, 2012 at 5:39 PM, Padmavathi Venna <padma.v@samsung.com> wrote:
> > +module_init(smdk_audio_init);
> > +module_exit(smdk_audio_exit);
> Ping. Any comments on this patch?
Don't send contentless pings and delete irrelevant context from replies.
Please refer to the feedback I sent in response to Sangbeom's pull
request - in short, this isn't the way to do this - do what the other
platforms do.
-------------- 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/20121126/226146c4/attachment.sig>
next prev parent reply other threads:[~2012-11-26 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 12:09 [RFC PATCH] ASoC: Samsung: Register the audio dma platform device Padmavathi Venna
2012-11-14 12:09 ` Padmavathi Venna
2012-11-14 12:09 ` [RFC PATCH] ASoC: Samsung: Register the audio " Padmavathi Venna
2012-11-14 12:09 ` Padmavathi Venna
2012-11-23 11:31 ` Padma Venkat
2012-11-23 11:31 ` Padma Venkat
2012-11-26 14:45 ` Padma Venkat
2012-11-26 14:45 ` Padma Venkat
2012-11-26 14:49 ` Mark Brown [this message]
2012-11-26 14:49 ` Mark Brown
2012-11-23 11:31 ` [RFC PATCH] ASoC: Samsung: Register the audio dma " Padma Venkat
2012-11-23 11:31 ` Padma Venkat
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=20121126144943.GM9411@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=padma.kvr@gmail.com \
--cc=padma.v@samsung.com \
--cc=sbkim73@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 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.