From: Vinod Koul <vinod.koul@intel.com>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Dan Williams <dan.j.williams@intel.com>,
Mark Brown <broonie@kernel.org>, Andy Green <andy@warmcat.com>
Subject: Re: [PATCH 0/7 v5] K3DMA fixes for HiKey HDMI audio
Date: Wed, 31 Aug 2016 10:10:01 +0530 [thread overview]
Message-ID: <20160831044001.GS9355@localhost> (raw)
In-Reply-To: <1472491853-15644-1-git-send-email-john.stultz@linaro.org>
On Mon, Aug 29, 2016 at 10:30:46AM -0700, John Stultz wrote:
> Just sending these the k3dma fixes and cyclic mode patches
> needed to support audio on HiKey, hopefully one last time. :)
>
> Again, no code changes here, but I did re-order the Kconfig
> chnage to be last to avoid a bisection build issue on i386
> w/ COMPILE_TEST that the kbuild test bot found.
Applied all, thanks
--
~Vinod
prev parent reply other threads:[~2016-08-31 4:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 17:30 [PATCH 0/7 v5] K3DMA fixes for HiKey HDMI audio John Stultz
2016-08-29 17:30 ` [PATCH 1/7 v5] k3dma: Fix hisi burst clipping John Stultz
2016-08-29 17:30 ` [PATCH 2/7 v5] k3dma: Fix dma err offsets John Stultz
2016-08-29 17:30 ` [PATCH 3/7 v5] k3dma: Fix "nobody cared" message seen on any error John Stultz
2016-08-29 17:30 ` [PATCH 4/7 v5] k3dma: Fix occasional DMA ERR issue by using proper dma api John Stultz
2016-08-29 17:30 ` [PATCH 5/7 v5] k3dma: Fix memory handling in preparation for cyclic mode John Stultz
2016-08-29 17:30 ` [PATCH 6/7 v5] k3dma: Add cyclic mode for audio John Stultz
2016-08-29 17:30 ` [PATCH 7/7 v5] Kconfig: Allow k3dma driver to be selected for more then HISI3xx platforms John Stultz
2016-08-31 4:40 ` Vinod Koul [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=20160831044001.GS9355@localhost \
--to=vinod.koul@intel.com \
--cc=andy@warmcat.com \
--cc=broonie@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=john.stultz@linaro.org \
--cc=k.kozlowski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=zhangfei.gao@linaro.org \
/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