mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Xiaohui Zhang <ruc_zhangxiaohui@163.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
	luiz.dentz@gmail.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com,
	linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, xiaohuizhang@ruc.edu.cn
Subject: Re: [PATCH 1/1] Bluetooth: use memset avoid memory leaks
Date: Wed, 08 Jun 2022 17:00:14 +0000	[thread overview]
Message-ID: <165470761443.24378.11011419118716998242.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220607153020.29430-1-ruc_zhangxiaohui@163.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Marcel Holtmann <marcel@holtmann.org>:

On Tue,  7 Jun 2022 23:30:20 +0800 you wrote:
> From: Xiaohui Zhang <xiaohuizhang@ruc.edu.cn>
> 
> Similar to the handling of l2cap_ecred_connect in commit d3715b2333e9
> ("Bluetooth: use memset avoid memory leaks"), we thought a patch
> might be needed here as well.
> 
> Use memset to initialize structs to prevent memory leaks
> in l2cap_le_connect
> 
> [...]

Here is the summary with links:
  - [1/1] Bluetooth: use memset avoid memory leaks
    https://git.kernel.org/bluetooth/bluetooth-next/c/0b537674e072

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



      reply	other threads:[~2022-06-08 17:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 15:30 Xiaohui Zhang
2022-06-08 17:00 ` patchwork-bot+bluetooth [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=165470761443.24378.11011419118716998242.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ruc_zhangxiaohui@163.com \
    --cc=xiaohuizhang@ruc.edu.cn \
    /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®