All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: tiwai@suse.de, Jeeja KP <jeeja.kp@intel.com>,
	alsa-devel@alsa-project.org, liam.r.girdwood@intel.com
Subject: Re: [PATCH 1/2] ASoC: compress - add support for metadata apis
Date: Mon, 18 Feb 2013 19:05:13 +0530	[thread overview]
Message-ID: <20130218133513.GA10950@intel.com> (raw)
In-Reply-To: <20130218131928.GB30157@opensource.wolfsonmicro.com>

On Mon, Feb 18, 2013 at 01:19:28PM +0000, Mark Brown wrote:
> On Mon, Feb 18, 2013 at 03:59:40PM +0530, Vinod Koul wrote:
> 
> > Mark, Takashi:
> > How do you guys wnat to take this one, Ideally this should go to mark's tree but
> > the dependent apis are in takashi's tree, either way is fine with me :)
> 
> Since we're expecting the merge window to open today or something
> probably the easiest thing is for me to apply it after -rc1?
okay, but it can go via takashi's tree after he merges asoc updates from you.
Since core support is getting into linus's tree in merge window it would make
sense for ASoC and driver update to go along as well.

--
~Vinod

  reply	other threads:[~2013-02-18 13:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 10:29 [PATCH 1/2] ASoC: compress - add support for metadata apis Vinod Koul
2013-02-18 10:29 ` [PATCH 2/2] ASoC: mid-x86 - add support for metedata apis Vinod Koul
2013-02-18 13:19 ` [PATCH 1/2] ASoC: compress - add support for metadata apis Mark Brown
2013-02-18 13:35   ` Vinod Koul [this message]
2013-02-18 14:35     ` Mark Brown
2013-03-21  4:31       ` Vinod Koul
2013-03-21 15:24         ` Mark Brown
2013-03-22 10:57 ` Mark Brown
2013-03-26 15:52 Vinod Koul
2013-03-26 17:46 ` 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=20130218133513.GA10950@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jeeja.kp@intel.com \
    --cc=liam.r.girdwood@intel.com \
    --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 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.