From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Chavan <ashish.chavan@kpitcummins.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>,
David Dajun Chen <david.chen@diasemi.com>
Subject: Re: [PATCH] ASoC: Convert DA7210 to table based DAPM init
Date: Mon, 17 Oct 2011 22:38:46 +0100 [thread overview]
Message-ID: <20111017213846.GB5200@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1318665460.613.3.camel@matrix>
On Sat, Oct 15, 2011 at 01:27:40PM +0530, Ashish Chavan wrote:
> Is this already applied? Some how I am unable to sync my tree as of now.
Yes, for something trivial like this that's obviously correct if it
builds I'll generally just go ahead and apply it.
prev parent reply other threads:[~2011-10-17 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 19:28 [PATCH] ASoC: Convert DA7210 to table based DAPM init Mark Brown
2011-10-15 7:57 ` Ashish Chavan
2011-10-17 21:38 ` 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=20111017213846.GB5200@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ashish.chavan@kpitcummins.com \
--cc=david.chen@diasemi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).