From: Vinod Koul <vkoul@kernel.org>
To: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
"Nuno Sá" <nuno.sa@analog.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>, Frank Li <Frank.Li@kernel.org>
Subject: Re: [PATCH v4 0/4] dmaengine: dma-axi-dmac: Some memory related fixes
Date: Mon, 08 Jun 2026 17:43:21 +0530 [thread overview]
Message-ID: <178092080107.96550.13783888741003306021.b4-ty@kernel.org> (raw)
In-Reply-To: <20260424-dma-dmac-handle-vunmap-v4-0-90f43412fdc0@analog.com>
On Fri, 24 Apr 2026 18:40:13 +0100, Nuno Sá wrote:
> Here it goes v3. Given there are some discussions about adding devlinks
> in damengine, I dropped the patch implementing the .device_release() for
> now.
>
>
Applied, thanks!
[1/4] dmaengine: Fix possible use after free
commit: 92f853f0645aebf1d05d333e97ab7c342ace1892
[2/4] dmaengine: dma-axi-dmac: Properly free struct axi_dmac_desc
commit: 4910ce1b3b35687bb2a5e742c4bfbea3c647c980
[3/4] dmaengine: dma-axi-dmac: Drop struct clk from main struct
commit: a725ac2055271fe8123fa854bfeff6e349f7cf0e
[4/4] dmaengine: dma-axi-dmac: use DMA pool to manange DMA descriptor
commit: 9e942c8579130e62734c14338e9f451780669164
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-06-08 12:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 17:40 Nuno Sá via B4 Relay
2026-04-24 17:40 ` [PATCH v4 1/4] dmaengine: Fix possible use after free Nuno Sá via B4 Relay
2026-05-07 18:33 ` Frank Li
2026-04-24 17:40 ` [PATCH v4 2/4] dmaengine: dma-axi-dmac: Properly free struct axi_dmac_desc Nuno Sá via B4 Relay
2026-05-07 18:33 ` Frank Li
2026-04-24 17:40 ` [PATCH v4 3/4] dmaengine: dma-axi-dmac: Drop struct clk from main struct Nuno Sá via B4 Relay
2026-05-07 18:34 ` Frank Li
2026-04-24 17:40 ` [PATCH v4 4/4] dmaengine: dma-axi-dmac: use DMA pool to manange DMA descriptor Nuno Sá via B4 Relay
2026-05-07 18:37 ` Frank Li
2026-06-08 12:13 ` 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=178092080107.96550.13783888741003306021.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®