From: patchwork-bot+bluetooth@kernel.org
To: Thorsten Blum <thorsten.blum@toblux.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btintel_pcie: Remove unnecessary memset(0) calls
Date: Mon, 03 Jun 2024 13:00:30 +0000 [thread overview]
Message-ID: <171741963022.17349.8989919081821118644.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240531235132.664665-2-thorsten.blum@toblux.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 1 Jun 2024 01:51:33 +0200 you wrote:
> Remove memset(0) after dma_alloc_coherent(), which already zeroes out
> the memory, and fix the following two Coccinelle/coccicheck warnings
> reported by zalloc-simple.cocci:
>
> btintel_pcie.c:837:19-37: WARNING: dma_alloc_coherent used in
>
> /* Allocate full chunk of data buffer for DMA first and do indexing and
> * initialization next, so it can be freed easily
> */
> rxq->buf_v_addr already zeroes out memory, so memset is not needed
>
> [...]
Here is the summary with links:
- Bluetooth: btintel_pcie: Remove unnecessary memset(0) calls
https://git.kernel.org/bluetooth/bluetooth-next/c/c137bc53035c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-06-03 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 23:51 [PATCH] Bluetooth: btintel_pcie: Remove unnecessary memset(0) calls Thorsten Blum
2024-06-01 1:12 ` bluez.test.bot
2024-06-03 13: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=171741963022.17349.8989919081821118644.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=thorsten.blum@toblux.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 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 NNTP newsgroup(s).