From: Vinod Koul <vinod.koul@intel.com>
To: "Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
Cc: tiwai@suse.de, patches.audio@intel.com,
alsa-devel@alsa-project.org, broonie@kernel.org,
lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: Intel: Skylake: Fix default dma_buffer_size
Date: Mon, 3 Jul 2017 16:40:44 +0530 [thread overview]
Message-ID: <20170703111044.GC19154@localhost> (raw)
In-Reply-To: <1498828124-17671-1-git-send-email-subhransu.s.prusty@intel.com>
On Fri, Jun 30, 2017 at 06:38:44PM +0530, Subhransu S. Prusty wrote:
> If the dma_buffer_size is not defined in topology, fix it to 2ms default
> value to make backward compatible.
Acked-By: Vinod Koul <vinod.koul@intel.com>
--
~Vinod
next prev parent reply other threads:[~2017-07-03 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 13:08 [PATCH] ASoC: Intel: Skylake: Fix default dma_buffer_size Subhransu S. Prusty
2017-07-03 11:10 ` Vinod Koul [this message]
2017-07-10 18:41 ` Applied "ASoC: Intel: Skylake: Fix default dma_buffer_size" 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=20170703111044.GC19154@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=patches.audio@intel.com \
--cc=subhransu.s.prusty@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 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).