[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <83ffe78c-3c3b-a1a3-ae17-90a0a1f4da93@oracle.com>
Date: Thu, 6 Aug 2020 10:58:34 -0700
From: santosh.shilimkar@...cle.com
To: Grygorii Strashko <grygorii.strashko@...com>,
Vinod Koul <vkoul@...nel.org>,
Peter Ujfalusi <peter.ujfalusi@...com>
Cc: ssantosh@...nel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, dmaengine@...r.kernel.org
Subject: Re: [PATCH] dmaengine: ti: k3-udma-glue: Fix parameters for rx ring
pair request
On 8/5/20 6:17 AM, Grygorii Strashko wrote:
>
>
> On 05/08/2020 14:32, Vinod Koul wrote:
>> On 05-08-20, 14:27, Peter Ujfalusi wrote:
>>> The original commit mixed up the forward and completion ring IDs for the
>>> rx flow configuration.
>>
>> Acked-By: Vinod Koul <vkoul@...nel.org>
>>
>>>
>>> Fixes: 4927b1ab2047 ("dmaengine: ti: k3-udma: Switch to
>>> k3_ringacc_request_rings_pair")
>>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@...com>
>>> ---
>>> Hi Santosh, Vinod,
>>>
>>> the offending patch was queued via ti SoC tree.
>>> Santosh, can you pick up this fix also?
>
> Thank you Peter for catching this - it's valid issue.
> but I'd like to note that issue was discovered with private code and
> nothing is broken in Master.
>
> Reviewed-by: Grygorii Strashko <grygorii.strashko@...com>
>
Will queue this up for next merge window.
regards,
Santosh
Powered by blists - more mailing lists