From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1 1/2] Bluetooth: Fix NULL pointer deference on eir_get_service_data
Date: Thu, 05 Jun 2025 19:20:28 +0000 [thread overview]
Message-ID: <174915122875.3205310.8740710645862296239.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250605152316.807664-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 5 Jun 2025 11:23:15 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> The len parameter is considered optional so it can be NULL so it cannot
> be used for skipping to next entry of EIR_SERVICE_DATA.
>
> Fixes: 8f9ae5b3ae80 ("Bluetooth: eir: Add helpers for managing service data")
> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> [...]
Here is the summary with links:
- [v1,1/2] Bluetooth: Fix NULL pointer deference on eir_get_service_data
https://git.kernel.org/bluetooth/bluetooth-next/c/8dfaf658a378
- [v1,2/2] Bluetooth: hci_sync: Fix broadcast/PA when using an existing instance
https://git.kernel.org/bluetooth/bluetooth-next/c/7615e0c7b24a
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-06-05 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 15:23 [PATCH v1 1/2] Bluetooth: Fix NULL pointer deference on eir_get_service_data Luiz Augusto von Dentz
2025-06-05 15:23 ` [PATCH v1 2/2] Bluetooth: hci_sync: Fix broadcast/PA when using an existing instance Luiz Augusto von Dentz
2025-06-05 16:02 ` [v1,1/2] Bluetooth: Fix NULL pointer deference on eir_get_service_data bluez.test.bot
2025-06-05 19:20 ` 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=174915122875.3205310.8740710645862296239.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox