From: Vinod Koul <vkoul@kernel.org>
To: Paul Cercueil <paul@crapouillou.net>
Cc: od@zcrc.me, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] dmaengine: dma-jz4780: Also break descriptor chains on JZ4725B
Date: Wed, 11 Dec 2019 16:26:08 +0530 [thread overview]
Message-ID: <20191211105608.GH2536@vkoul-mobl> (raw)
In-Reply-To: <20191210165545.59690-1-paul@crapouillou.net>
On 10-12-19, 17:55, Paul Cercueil wrote:
> It turns out that the JZ4725B displays the same buggy behaviour as the
> JZ4740 that was described in commit f4c255f1a747 ("dmaengine: dma-jz4780:
> Break descriptor chains on JZ4740").
>
> Work around it by using the same workaround previously used for the
> JZ4740.
>
> Fixes commit f4c255f1a747 ("dmaengine: dma-jz4780: Break descriptor
> chains on JZ4740")
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2019-12-11 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 16:55 [PATCH] dmaengine: dma-jz4780: Also break descriptor chains on JZ4725B Paul Cercueil
2019-12-11 10:56 ` 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=20191211105608.GH2536@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=od@zcrc.me \
--cc=paul@crapouillou.net \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).