From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: anish kumar <yesanishhere@gmail.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
"broonie@kernel.org" <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
tiwai@suse.com
Subject: Re: [PATCH] Codec to codec dai link description
Date: Mon, 24 Oct 2016 09:13:43 +0100 [thread overview]
Message-ID: <20161024081343.GQ3207@localhost.localdomain> (raw)
In-Reply-To: <CABCoZhB6F9J0677swtrHdp=Yg_v6b=C9Ph5KhWqaDN=3UjwqkA@mail.gmail.com>
On Sun, Oct 23, 2016 at 09:03:53PM -0700, anish kumar wrote:
> Signed-off-by: anish kumar <yesanishhere@gmail.com>
> ---
Acked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Thanks,
Charles
next prev parent reply other threads:[~2016-10-24 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 6:00 [PATCH] Codec to codec dai link description anish kumar
2016-10-20 9:44 ` Charles Keepax
2016-10-24 4:03 ` anish kumar
2016-10-24 8:13 ` Charles Keepax [this message]
2016-10-26 10:31 ` Mark Brown
2016-10-26 10:46 ` Applied "ASoC: Codec to codec dai link description" to the asoc tree 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=20161024081343.GQ3207@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=tiwai@suse.com \
--cc=yesanishhere@gmail.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).