From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: pl330: fix bug that cause start the same descs in cyclic
Date: Tue, 10 Feb 2015 16:14:28 -0800 [thread overview]
Message-ID: <20150211001428.GA21387@intel.com> (raw)
In-Reply-To: <1418038100-4316-1-git-send-email-addy.ke@rock-chips.com>
On Mon, Dec 08, 2014 at 07:28:20PM +0800, Addy Ke wrote:
> This bug will cause NULL pointer after commit dfac17, and cause
> wrong package in I2S DMA transfer before commit dfac17.
>
Applied, thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Addy Ke <addy.ke@rock-chips.com>
Cc: dan.j.williams@intel.com, heiko@sntech.de, olof@lixom.net,
dianders@chromium.org, amstan@chromium.org,
sonnyrao@chromium.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, cf@rock-chips.com,
xjq@rock-chips.com, huangtao@rock-chips.com, zyw@rock-chips.com,
yzq@rock-chips.com, hj@rock-chips.com, kever.yang@rock-chips.com,
hl@rock-chips.com, caesar.wang@rock-chips.com,
zhengsq@rock-chips.com, jason.song@rock-chips.com,
hhb@rock-chips.com
Subject: Re: [PATCH] dmaengine: pl330: fix bug that cause start the same descs in cyclic
Date: Tue, 10 Feb 2015 16:14:28 -0800 [thread overview]
Message-ID: <20150211001428.GA21387@intel.com> (raw)
In-Reply-To: <1418038100-4316-1-git-send-email-addy.ke@rock-chips.com>
On Mon, Dec 08, 2014 at 07:28:20PM +0800, Addy Ke wrote:
> This bug will cause NULL pointer after commit dfac17, and cause
> wrong package in I2S DMA transfer before commit dfac17.
>
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2015-02-11 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 11:28 [PATCH] dmaengine: pl330: fix bug that cause start the same descs in cyclic Addy Ke
2014-12-08 11:28 ` Addy Ke
2015-02-11 0:14 ` Vinod Koul [this message]
2015-02-11 0:14 ` Vinod Koul
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=20150211001428.GA21387@intel.com \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.