Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: rajeev <rajeev-dlh.kumar@st.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH V3 1/5] sound: asoc: Adding support for STA529 Audio Codec
Date: Wed, 20 Apr 2011 17:11:41 +0530	[thread overview]
Message-ID: <4DAEC675.50300@st.com> (raw)
In-Reply-To: <20110420105620.GB4097@opensource.wolfsonmicro.com>

Hi Mark
     
On 4/20/2011 4:26 PM, Mark Brown wrote:
> On Wed, Apr 20, 2011 at 09:54:47AM +0530, rajeev wrote:
>> On 4/11/2011 8:26 PM, Mark Brown wrote:
>>> On Mon, Apr 11, 2011 at 11:00:00AM +0530, Rajeev Kumar wrote:
> 
>>>> +static const char *op_mode_text[] = { "slave", "master"};
> 
>>> What is op_mode?  This sounds like it should be configured by
>>> set_dai_fmt()...
> 
>> OK, I will change the name.
> 
> You're missing the point here.  The name isn't an issue.
> 
Oops
Got the point, ThanX

>> This patch set has been compiled and tested for Linux-kernel-version 2.6.38-rc4,
>> since SPEAr patches for this linux version are already under review in Russel King's
>> ARM branch.This version does not have snd_soc_cache_sync() function. 
> 
> This isn't how mainline works.  You're not submitting code against some
> old, released kernel version.  You're submitting code for the
> development version of the kernel and need to fit in with that.  Code
> for an older kernel may not even compile with current development
> kernels.  For integration testing -next is often a good bet.
> .
> 
OK, I will do the changes as per your guidelines.

best rgds
Rajeev

  reply	other threads:[~2011-04-20 11:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11  5:29 [PATCH V3 0/5] Adding ASoC drivers for SPEAr13XX platform Rajeev Kumar
2011-04-11  5:30 ` [PATCH V3 1/5] sound: asoc: Adding support for STA529 Audio Codec Rajeev Kumar
2011-04-11  5:30   ` [PATCH V3 2/5] sound: asoc: Adding support for SPEAr13XX ASoC platform driver Rajeev Kumar
2011-04-11  5:30     ` [PATCH V3 3/5] sound: asoc: Adding support for SPEAr13XX ASoC machine driver Rajeev Kumar
2011-04-11  5:30       ` [PATCH V3 4/5] sound: asoc: Adding Kconfig and Makefile to support SPEAr13XX ASoC driver Rajeev Kumar
2011-04-11  5:30         ` [PATCH V3 5/5] sound: asoc: Adding support for SPEAr13XX in soc Rajeev Kumar
2011-04-11 13:00     ` [PATCH V3 2/5] sound: asoc: Adding support for SPEAr13XX ASoC platform driver Lu Guanqun
2011-04-18  5:00       ` rajeev
2011-04-11 12:53   ` [PATCH V3 1/5] sound: asoc: Adding support for STA529 Audio Codec Lu Guanqun
2011-04-11 13:35     ` Mark Brown
2011-04-11 15:09       ` Lu Guanqun
2011-04-11 23:54         ` Mark Brown
2011-04-12  0:06           ` Lu Guanqun
2011-04-11 14:56   ` Mark Brown
2011-04-14  9:54     ` Takashi Iwai
2011-04-14 12:18       ` Mark Brown
2011-04-14 12:25         ` Takashi Iwai
2011-04-14 14:19       ` Lu Guanqun
2011-04-14 14:28         ` Lu Guanqun
2011-04-15  9:27           ` Takashi Iwai
2011-04-15 14:10             ` Lu Guanqun
2011-04-15  9:23         ` Takashi Iwai
2011-04-20  4:24     ` rajeev
2011-04-20 10:56       ` Mark Brown
2011-04-20 11:41         ` rajeev [this message]
2011-04-20 11:42         ` rajeev
2011-04-11 15:45   ` Lu Guanqun

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=4DAEC675.50300@st.com \
    --to=rajeev-dlh.kumar@st.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox