Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 0/5] shared: Use util_iov helpers in gatt-db, hog, asha and micp
Date: Thu, 12 Nov 2026 17:50:08 +0000	[thread overview]
Message-ID: <179450580827.563116.10974231348534576330.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261111203949.3874673-1-luiz.dentz@gmail.com>

Hello:

This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Wed, 11 Nov 2026 15:39:44 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> This continues the conversion of the GATT code in src/shared to the
> util_iov_pull_* and util_iov_push_* helpers, so that the bounds check is
> part of the access, now for gatt-db and the HoG, ASHA and MICP profiles.
> 
> The conversions are meant to be behavior preserving and are covered by
> the existing unit tests (test-gatt, test-hog, test-micp). The existing
> code already checked the lengths in the HoG and ASHA readers, so no new
> tests were added for them.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2,1/5] shared/gatt-db: Use util_iov helpers to build and parse values
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c37508359cbe
  - [BlueZ,v2,2/5] shared/hog: Use util_iov helpers to parse characteristic values
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=628a84f214e4
  - [BlueZ,v2,3/5] shared/asha: Use util_iov helpers to parse characteristic values
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a848a36c8154
  - [BlueZ,v2,4/5] shared/micp: Fix reading Mute State from an empty notification
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ebc4876e895b
  - [BlueZ,v2,5/5] shared/micp: Use util_iov_pull_mem instead of a local helper
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1bd266143b3a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-12 17:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 20:39 [PATCH BlueZ v2 0/5] shared: Use util_iov helpers in gatt-db, hog, asha and micp Luiz Augusto von Dentz
2026-11-11 20:39 ` [PATCH BlueZ v2 1/5] shared/gatt-db: Use util_iov helpers to build and parse values Luiz Augusto von Dentz
2026-11-12  2:09   ` shared: Use util_iov helpers in gatt-db, hog, asha and micp bluez.test.bot
2026-11-11 20:39 ` [PATCH BlueZ v2 2/5] shared/hog: Use util_iov helpers to parse characteristic values Luiz Augusto von Dentz
2026-11-11 20:39 ` [PATCH BlueZ v2 3/5] shared/asha: " Luiz Augusto von Dentz
2026-11-11 20:39 ` [PATCH BlueZ v2 4/5] shared/micp: Fix reading Mute State from an empty notification Luiz Augusto von Dentz
2026-11-11 20:39 ` [PATCH BlueZ v2 5/5] shared/micp: Use util_iov_pull_mem instead of a local helper Luiz Augusto von Dentz
2026-11-12 17:50 ` 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=179450580827.563116.10974231348534576330.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