mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: jiaheng.fan@nxp.com, peng.ma@nxp.com, wen.he_1@nxp.com,
	 Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	 kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/3] dmaengine: fsl-qdma: Fix some error handling paths
Date: Mon, 22 Jan 2024 21:55:10 +0530	[thread overview]
Message-ID: <170594071003.297861.1425725025349258769.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1704621515.git.christophe.jaillet@wanadoo.fr>


On Sun, 07 Jan 2024 11:02:02 +0100, Christophe JAILLET wrote:
> The first 2 patches are bug fixes related to missing dma_free_coherent() either
> in the remove function or in the error handling path of the probe.
> 
> They are compile tested only. So review with care.
> 
> The 3rd patch is only a clean up.
> 
> [...]

Applied, thanks!

[1/3] dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA
      commit: 968bc1d7203d384e72afe34124a1801b7af76514
[2/3] dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA
      commit: 3aa58cb51318e329d203857f7a191678e60bb714
[3/3] dmaengine: fsl-qdma: Remove a useless devm_kfree()
      commit: 0650006a93a2ce3b57f86e7f000347d9ae7737ef

Best regards,
-- 
~Vinod



      parent reply	other threads:[~2024-01-22 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-07 10:02 Christophe JAILLET
2024-01-07 10:02 ` [PATCH 1/3] dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA Christophe JAILLET
2024-01-07 10:02 ` [PATCH 2/3] dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA Christophe JAILLET
2024-01-07 10:02 ` [PATCH 3/3] dmaengine: fsl-qdma: Remove a useless devm_kfree() Christophe JAILLET
2024-01-22 16:25 ` 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=170594071003.297861.1425725025349258769.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=dmaengine@vger.kernel.org \
    --cc=jiaheng.fan@nxp.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.ma@nxp.com \
    --cc=wen.he_1@nxp.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®