From: Conor Dooley <conor@kernel.org>
To: green.wan@sifive.com, vkoul@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, conor+dt@kernel.org,
shravan chippa <shravan.chippa@microchip.com>
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
nagasuresh.relli@microchip.com, praveen.kumar@microchip.com
Subject: Re: (subset) [PATCH v5 0/4] dma: sf-pdma: various sf-pdma updates for the mpfs platform
Date: Tue, 6 Feb 2024 19:39:25 +0000 [thread overview]
Message-ID: <20240206-luckily-udder-ffd828ccdc57@spud> (raw)
In-Reply-To: <20231208103856.3732998-1-shravan.chippa@microchip.com>
From: Conor Dooley <conor.dooley@microchip.com>
On Fri, 08 Dec 2023 16:08:52 +0530, shravan chippa wrote:
> From: Shravan Chippa <shravan.chippa@microchip.com>
>
> Changes from V4 -> V5:
>
> Modified commit msg
> Replaced the sf_pdma_of_xlate() function with
> of_dma_xlate_by_chan_id()
>
> [...]
Applied to riscv-dt-for-next, thanks!
[4/4] riscv: dts: microchip: add specific compatible for mpfs pdma
https://git.kernel.org/conor/c/5669bb5a16a0
Thanks,
Conor.
prev parent reply other threads:[~2024-02-06 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 10:38 [PATCH v5 0/4] dma: sf-pdma: various sf-pdma updates for the mpfs platform shravan chippa
2023-12-08 10:38 ` [PATCH v5 1/4] dmaengine: sf-pdma: Support of_dma_controller_register() shravan chippa
2023-12-08 10:38 ` [PATCH v5 2/4] dt-bindings: dma: sf-pdma: add new compatible name shravan chippa
2023-12-08 10:38 ` [PATCH v5 3/4] dmaengine: sf-pdma: add mpfs-pdma " shravan chippa
2023-12-08 10:38 ` [PATCH v5 4/4] riscv: dts: microchip: add specific compatible for mpfs pdma shravan chippa
2023-12-11 15:04 ` (subset) [PATCH v5 0/4] dma: sf-pdma: various sf-pdma updates for the mpfs platform Vinod Koul
2024-02-06 19:39 ` Conor Dooley [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=20240206-luckily-udder-ffd828ccdc57@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=green.wan@sifive.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nagasuresh.relli@microchip.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=praveen.kumar@microchip.com \
--cc=robh+dt@kernel.org \
--cc=shravan.chippa@microchip.com \
--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