From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Vinod Koul <vkoul@kernel.org>, Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: dmaengine@vger.kernel.org, santosh.shilimkar@oracle.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, ssantosh@kernel.org
Subject: Re: [PATCH] dmaengine: ti: k3-udma-glue: Fix parameters for rx ring pair request
Date: Wed, 5 Aug 2020 16:17:24 +0300 [thread overview]
Message-ID: <3eea63fe-88f5-d6b6-433a-bb15495a839d@ti.com> (raw)
In-Reply-To: <20200805113237.GX12965@vkoul-mobl>
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@kernel.org>
>
>>
>> Fixes: 4927b1ab2047 ("dmaengine: ti: k3-udma: Switch to k3_ringacc_request_rings_pair")
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.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@ti.com>
--
Best regards,
grygorii
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-05 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 11:27 [PATCH] dmaengine: ti: k3-udma-glue: Fix parameters for rx ring pair request Peter Ujfalusi
2020-08-05 11:32 ` Vinod Koul
2020-08-05 13:17 ` Grygorii Strashko [this message]
2020-08-06 17:58 ` santosh.shilimkar
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=3eea63fe-88f5-d6b6-433a-bb15495a839d@ti.com \
--to=grygorii.strashko@ti.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@kernel.org \
--cc=vkoul@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