All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btqcomsmd: Fix a resource leak in error handling paths in the probe function
Date: Mon, 01 Mar 2021 19:59:42 +0000	[thread overview]
Message-ID: <161462878254.6187.945374265511311276.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201212094658.83861-1-christophe.jaillet@wanadoo.fr>

Hello:

This patch was applied to qcom/linux.git (refs/heads/for-next):

On Sat, 12 Dec 2020 10:46:58 +0100 you wrote:
> Some resource should be released in the error handling path of the probe
> function, as already done in the remove function.
> 
> The remove function was fixed in commit 5052de8deff5 ("soc: qcom: smd:
> Transition client drivers from smd to rpmsg")
> 
> Fixes: 1511cc750c3d ("Bluetooth: Introduce Qualcomm WCNSS SMD based HCI driver")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> 
> [...]

Here is the summary with links:
  - Bluetooth: btqcomsmd: Fix a resource leak in error handling paths in the probe function
    https://git.kernel.org/qcom/c/9a39a927be01

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-03-01 20:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-12  9:46 [PATCH] Bluetooth: btqcomsmd: Fix a resource leak in error handling paths in the probe function Christophe JAILLET
2020-12-12  9:46 ` Christophe JAILLET
2020-12-12 11:06 ` bluez.test.bot
2020-12-18 21:21 ` [PATCH] " Marcel Holtmann
2020-12-18 21:21   ` Marcel Holtmann
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm [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=161462878254.6187.945374265511311276.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=linux-arm-msm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.