From: Vinod Koul <vkoul@kernel.org>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Sekhar Nori <nsekhar@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Vignesh Raghavendra <vigneshr@ti.com>,
dmaengine@vger.kernel.org
Subject: Re: [PATCH next 6/6] dmaengine: ti: k3-udma: Switch to k3_ringacc_request_rings_pair
Date: Thu, 2 Jul 2020 18:27:05 +0530 [thread overview]
Message-ID: <20200702125705.GB273932@vkoul-mobl> (raw)
In-Reply-To: <20200701103030.29684-7-grygorii.strashko@ti.com>
On 01-07-20, 13:30, Grygorii Strashko wrote:
> From: Peter Ujfalusi <peter.ujfalusi@ti.com>
>
> We only request ring pairs via K3 DMA driver, switch to use the new
> k3_ringacc_request_rings_pair() to simplify the code.
Acked-By: Vinod Koul <vkoul@kernel.org>
--
~Vinod
next prev parent reply other threads:[~2020-07-02 12:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 10:30 [PATCH next 0/6] soc: ti: k3-ringacc: updates Grygorii Strashko
2020-07-01 10:30 ` [PATCH next 1/6] dt-bindings: soc: ti: k3-ringacc: convert bindings to json-schema Grygorii Strashko
2020-07-15 9:40 ` Grygorii Strashko
2020-07-01 10:30 ` [PATCH next 2/6] soc: ti: k3-ringacc: Move state tracking variables under a struct Grygorii Strashko
2020-07-01 10:30 ` [PATCH next 3/6] soc: ti: k3-ringacc: add ring's flags to dump Grygorii Strashko
2020-07-01 10:30 ` [PATCH next 4/6] soc: ti: k3-ringacc: add request pair of rings api Grygorii Strashko
2020-07-01 11:54 ` Peter Ujfalusi
2020-07-01 12:12 ` Grygorii Strashko
2020-07-01 12:33 ` Peter Ujfalusi
2020-07-01 10:30 ` [PATCH next 5/6] soc: ti: k3-ringacc: separate soc specific initialization Grygorii Strashko
2020-07-01 10:30 ` [PATCH next 6/6] dmaengine: ti: k3-udma: Switch to k3_ringacc_request_rings_pair Grygorii Strashko
2020-07-02 12:57 ` Vinod Koul [this message]
2020-07-17 12:41 ` Grygorii Strashko
2020-07-08 8:33 ` [PATCH next 0/6] soc: ti: k3-ringacc: updates Peter Ujfalusi
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=20200702125705.GB273932@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.com \
/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).