From: patchwork-bot+bluetooth@kernel.org
To: Kang Minchul <tegongkang@gmail.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
Subject: Re: [PATCH] net: bluetooth: Use kzalloc instead of kmalloc/memset
Date: Mon, 31 Oct 2022 23:10:15 +0000 [thread overview]
Message-ID: <166725781597.15466.7988484635308964186.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221029204541.20967-1-tegongkang@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 30 Oct 2022 05:45:41 +0900 you wrote:
> This commit replace kmalloc + memset to kzalloc
> for better code readability and simplicity.
>
> Following messages are related cocci warnings.
>
> WARNING: kzalloc should be used for d, instead of kmalloc/memset
>
> [...]
Here is the summary with links:
- net: bluetooth: Use kzalloc instead of kmalloc/memset
https://git.kernel.org/bluetooth/bluetooth-next/c/214c507d87cc
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-31 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 20:45 [PATCH] net: bluetooth: Use kzalloc instead of kmalloc/memset Kang Minchul
2022-10-29 21:08 ` bluez.test.bot
2022-10-31 23:10 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-17 3:04 [PATCH] " Jiapeng Chong
2022-10-19 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=166725781597.15466.7988484635308964186.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=tegongkang@gmail.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 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.