Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-5072-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] Bluetooth: btintel_pcie: Remove unnecessary memset(0) calls
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <171741963022.17349.8989919081821118644.git-patchwork-notify@kernel.org>
Date: Mon, 03 Jun 2024 13:00:30 +0000
References: <20240531235132.664665-2-thorsten.blum@toblux.com>
In-Reply-To: <20240531235132.664665-2-thorsten.blum@toblux.com>
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

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