From: Mark Brown <broonie@kernel.org>
To: "Fang, Yang A" <yang.a.fang@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Koul, Vinod" <vinod.koul@intel.com>,
"Jain, Praveen K" <praveen.k.jain@intel.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"Iriawan, Denny" <denny.iriawan@intel.com>,
"Nujella, Sathyanarayana" <sathyanarayana.nujella@intel.com>,
"kevin.strasser@linux.intel.com" <kevin.strasser@linux.intel.com>
Subject: Re: [PATCH v3] ASoC: Intel: Support rt5650 codec for Cherrytrail & Braswell
Date: Wed, 29 Apr 2015 11:48:21 +0100 [thread overview]
Message-ID: <20150429104821.GD22845@sirena.org.uk> (raw)
In-Reply-To: <0485FB02182A4744A8B06D69AB7BF8E718CC3BFC@ORSMSX113.amr.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 224 bytes --]
On Wed, Apr 29, 2015 at 05:25:35AM +0000, Fang, Yang A wrote:
> May I ask which branch you are applied? I did not find it in
> topic/intel or for-next.
Applied means it's in my local tree, not that it's been published.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-04-29 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 23:35 [PATCH 1/2] ASoC: Intel: Support rt5650 codec for Cherrytrail & Braswell yang.a.fang
2015-04-21 23:36 ` [PATCH 2/2] ASoC: Intel: Add support rt5650 in sst driver yang.a.fang
2015-04-22 10:32 ` Mark Brown
2015-04-22 4:18 ` [PATCH 1/2] ASoC: Intel: Support rt5650 codec for Cherrytrail & Braswell Vinod Koul
2015-04-22 5:02 ` Yang Fang
2015-04-22 21:56 ` [PATCH v2] " yang.a.fang
2015-04-23 17:23 ` [PATCH v3] " yang.a.fang
2015-04-24 5:24 ` Vinod Koul
2015-04-24 12:44 ` Mark Brown
2015-04-29 5:25 ` Fang, Yang A
2015-04-29 10:48 ` Mark Brown [this message]
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=20150429104821.GD22845@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=denny.iriawan@intel.com \
--cc=kevin.strasser@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=praveen.k.jain@intel.com \
--cc=sathyanarayana.nujella@intel.com \
--cc=vinod.koul@intel.com \
--cc=yang.a.fang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox