All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashish Chavan <ashish.chavan@kpitcummins.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	"kuninori.morimoto.gx" <kuninori.morimoto.gx@renesas.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	David@alsa-project.org, Chen <david.chen@diasemi.com>,
	lrg <lrg@ti.com>
Subject: Re: [PATCH v8 3/3] ASoC: da7210: Add support for line input and mic
Date: Tue, 1 Nov 2011 18:20:42 +0530	[thread overview]
Message-ID: <1320151842.4064.10.camel@matrix> (raw)
In-Reply-To: <20111031125928.GC10217@opensource.wolfsonmicro.com>

On Mon, 2011-10-31 at 12:59 +0000, Mark Brown wrote:
> On Mon, Oct 31, 2011 at 02:55:39PM +0530, Ashish Chavan wrote:
> 
> > Is this really applied? I am looking at both for-3.2 and for-3.3
> > branches of linux-2.6-asoc.git and can only see commits till previous
> > one (i.e. ASoC: da7210: Add support for line out and DAC). I couldn't
> > find commit corresponding to this patch!
> 
> > Is there any other place to look for?
> 
> No, it mustn't have got out of my application queue for some reason.
> 

I see. It would be nice if you can let me know when you really apply it.

  reply	other threads:[~2011-11-01 12:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21 13:39 [PATCH v8 3/3] ASoC: da7210: Add support for line input and mic Ashish Chavan
2011-10-22  9:38 ` Mark Brown
2011-10-22  9:38   ` [alsa-devel] " Mark Brown
2011-10-25  3:59   ` Ashish P. Chavan
2011-10-25  7:09     ` [alsa-devel] " Mark Brown
2011-10-31  9:25   ` Ashish Chavan
2011-10-31 12:59     ` [alsa-devel] " Mark Brown
2011-11-01 12:50       ` Ashish Chavan [this message]
2011-11-01 12:54         ` Mark Brown
2011-11-01 12:54           ` [alsa-devel] " Mark Brown
2011-11-01 13:08           ` Ashish Chavan

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=1320151842.4064.10.camel@matrix \
    --to=ashish.chavan@kpitcummins.com \
    --cc=David@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=david.chen@diasemi.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.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.