From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/3] profiles/audio: Fix uninitialized params.subgroup_data warning
Date: Thu, 21 Aug 2025 17:30:06 +0000 [thread overview]
Message-ID: <175579740650.1124304.11801215010500519797.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250820141552.800720-1-hadess@hadess.net>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 20 Aug 2025 16:15:44 +0200 you wrote:
> profiles/audio/bass.c:923:2: uninit_use_in_call: Using uninitialized value "params". Field "params.subgroup_data" is uninitialized when calling "util_iov_append".
> ---
> profiles/audio/bass.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- [BlueZ,1/3] profiles/audio: Fix uninitialized params.subgroup_data warning
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c773fd53c953
- [BlueZ,2/3] tools/tester: Fix fd leaks
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=bb14a8b18f94
- [BlueZ,3/3] input: Fix incorrect destructors being used
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4784f58ff0ec
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:[~2025-08-21 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 14:15 [PATCH BlueZ 1/3] profiles/audio: Fix uninitialized params.subgroup_data warning Bastien Nocera
2025-08-20 14:15 ` [PATCH BlueZ 2/3] tools/tester: Fix fd leaks Bastien Nocera
2025-08-20 14:15 ` [PATCH BlueZ 3/3] input: Fix incorrect destructors being used Bastien Nocera
2025-08-20 15:52 ` [BlueZ,1/3] profiles/audio: Fix uninitialized params.subgroup_data warning bluez.test.bot
2025-08-21 17:30 ` 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=175579740650.1124304.11801215010500519797.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
/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.