imx.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: imx@lists.linux.dev, dmaengine@vger.kernel.org,
	 linux-kernel@vger.kernel.org, Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH 1/1] dmaengine: fsl-edma: fix miss mutex unlock at an error return path
Date: Thu, 18 Apr 2024 10:43:21 +0530	[thread overview]
Message-ID: <171341720175.758041.16850727320392721099.b4-ty@kernel.org> (raw)
In-Reply-To: <20240411203935.3137158-1-Frank.Li@nxp.com>


On Thu, 11 Apr 2024 16:39:35 -0400, Frank Li wrote:
> Use cleanup to manage mutex. Let compiler to do scope guard automatically.
> 
> 

Applied, thanks!

[1/1] dmaengine: fsl-edma: fix miss mutex unlock at an error return path
      commit: b52e28eca7da47fa389605a8eda1952a9fa3c69f

Best regards,
-- 
~Vinod



      reply	other threads:[~2024-04-18  5:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 20:39 [PATCH 1/1] dmaengine: fsl-edma: fix miss mutex unlock at an error return path Frank Li
2024-04-18  5: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=171341720175.758041.16850727320392721099.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=linux-kernel@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).