From: patchwork-bot+bluetooth@kernel•org
To: Jiapeng Chong <jiapeng.chong@linux•alibaba.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, abaci@linux•alibaba.com
Subject: Re: [PATCH] net: bluetooth: Use kzalloc instead of kmalloc/memset
Date: Wed, 19 Oct 2022 23:10:19 +0000 [thread overview]
Message-ID: <166622101976.13398.9806993237794232819.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221017030421.69108-1-jiapeng.chong@linux.alibaba.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel•com>:
On Mon, 17 Oct 2022 11:04:21 +0800 you wrote:
> Use kzalloc rather than duplicating its implementation, which makes code
> simple and easy to understand.
>
> ./net/bluetooth/hci_conn.c:2038:6-13: WARNING: kzalloc should be used for cp, instead of kmalloc/memset.
>
> Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=2406
> Reported-by: Abaci Robot <abaci@linux•alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux•alibaba.com>
>
> [...]
Here is the summary with links:
- net: bluetooth: Use kzalloc instead of kmalloc/memset
https://git.kernel.org/bluetooth/bluetooth-next/c/b0a19a2c4c53
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-10-19 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 3:04 [PATCH] net: bluetooth: Use kzalloc instead of kmalloc/memset Jiapeng Chong
2022-10-19 23:10 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-29 20:45 Kang Minchul
2022-10-31 23:10 ` patchwork-bot+bluetooth
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=166622101976.13398.9806993237794232819.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel$(echo .)org \
--cc=abaci@linux$(echo .)alibaba.com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=jiapeng.chong@linux$(echo .)alibaba.com \
--cc=johan.hedberg@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-bluetooth@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=luiz.dentz@gmail$(echo .)com \
--cc=marcel@holtmann$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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