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 v1 0/5] Make Notify Multiple timeout configurable
Date: Wed, 04 Nov 2026 19:10:08 +0000	[thread overview]
Message-ID: <179381940854.3059479.4187675660003846551.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261103203034.3904499-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 Tue,  3 Nov 2026 15:30:29 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> When acting as a HID device, GATT Notify Multiple adds up to 10 ms of
> latency to notifications since they are buffered to be aggregated into
> a single PDU. This set makes the timeout configurable with the new
> [GATT] NotifyMultiple option in main.conf:
> 
> [...]

Here is the summary with links:
  - [BlueZ,v1,1/5] shared/mainloop: Free removed idles without waiting for events
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2df553c447af
  - [BlueZ,v1,2/5] shared/mainloop: Fix idle ID overflow
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=833ebd7461cc
  - [BlueZ,v1,3/5] shared/gatt-server: Add bt_gatt_server_set_mnotify_timeout
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d39bf5ebc7c4
  - [BlueZ,v1,4/5] unit/test-gatt: Add Notify Multiple server tests
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=3894749d4f09
  - [BlueZ,v1,5/5] main.conf: Add NotifyMultiple option to GATT section
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0ee51551cf70

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-04 19:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 20:30 [PATCH BlueZ v1 0/5] Make Notify Multiple timeout configurable Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 1/5] shared/mainloop: Free removed idles without waiting for events Luiz Augusto von Dentz
2026-11-03 22:42   ` Make Notify Multiple timeout configurable bluez.test.bot
2026-11-03 20:30 ` [PATCH BlueZ v1 2/5] shared/mainloop: Fix idle ID overflow Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 3/5] shared/gatt-server: Add bt_gatt_server_set_mnotify_timeout Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 4/5] unit/test-gatt: Add Notify Multiple server tests Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 5/5] main.conf: Add NotifyMultiple option to GATT section Luiz Augusto von Dentz
2026-11-04 19:10 ` 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=179381940854.3059479.4187675660003846551.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