From: Vinod Koul <vkoul@kernel.org>
To: Frank Li <Frank.Li@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Koichiro Den <den@valinux.co.jp>
Cc: Devendra K Verma <devverma@amd.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/3] dmaengine: dw-edma: Prepare channels for remote use
Date: Mon, 05 Oct 2026 17:43:12 +0200 [thread overview]
Message-ID: <179121499286.358863.18382353505159158053.b4-ty@kernel.org> (raw)
In-Reply-To: <20260912174023.1227397-1-den@valinux.co.jp>
On Sun, 13 Sep 2026 02:40:20 +0900, Koichiro Den wrote:
> This small series contains standalone refactoring and new infrastructure
> for dmaengine and dw-edma.
>
> It prepares PCIe EPC-local DMA channels for remote use. The upcoming
> vNTB-embedded DMA support [1] will be the first user and depend on this
> series.
>
> [...]
Applied, thanks!
[1/3] dmaengine: Allow drivers to assign static channel IDs
commit: f54701da5c0562cefadc8b638c3c141111c10579
[2/3] dmaengine: dw-edma: Configure remote interrupt routing
commit: 9d31ad3b331d5d78bd6a247a9d35f35a6a9bbd59
[3/3] dmaengine: dw-edma: Account for the MSI vector offset
commit: 742c2a8041e8c23ec4ac6688284ac12c623df1cc
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-10-05 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 17:40 Koichiro Den
2026-09-12 17:40 ` [PATCH v4 1/3] dmaengine: Allow drivers to assign static channel IDs Koichiro Den
2026-09-12 17:40 ` [PATCH v4 2/3] dmaengine: dw-edma: Configure remote interrupt routing Koichiro Den
2026-09-14 15:22 ` Frank Li
2026-09-14 15:49 ` Koichiro Den
2026-09-14 15:53 ` Koichiro Den
2026-09-30 20:25 ` Frank Li
2026-10-01 6:07 ` Verma, Devendra
2026-10-30 15:58 ` Koichiro Den
2026-09-12 17:40 ` [PATCH v4 3/3] dmaengine: dw-edma: Account for the MSI vector offset Koichiro Den
2026-10-05 15:43 ` Vinod Koul [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=179121499286.358863.18382353505159158053.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=den@valinux.co.jp \
--cc=devverma@amd.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@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
all inboxes | Powered by JetHome®