Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?TmVib2rFoWEgQ3ZldGtvdmnEhyA8bmVia2F0QGdtYWlsLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH bluez] gatt-client: Fix not emitting MTU on reconnection
Date: Wed, 18 Nov 2026 19:20:12 +0000	[thread overview]
Message-ID: <179502961277.2490531.3324622150540616569.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261114-gatt-client-mtu-reconnect-v1-1-a86edc1eb208@gmail.com>

Hello:

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

On Sat, 14 Nov 2026 10:09:55 -0500 you wrote:
> From: Nebojša Cvetković <nebkat@gmail.com>
> 
> Characteristics kept across a disconnection have their MTU exchange
> callback registered on the bt_att of the connection they were created
> on, so no PropertiesChanged is emitted for MTU on later connections. As
> MTU is omitted while disconnected, a client that enumerated the objects
> in between has no MTU for the whole connection, and one that kept them
> has the value of the previous connection.
> 
> [...]

Here is the summary with links:
  - [bluez] gatt-client: Fix not emitting MTU on reconnection
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=cfd87b4970dc

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-18 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-14 15:09 [PATCH bluez] gatt-client: Fix not emitting MTU on reconnection Nebojša Cvetković via B4 Relay
2026-11-14 17:00 ` [bluez] " bluez.test.bot
2026-11-18 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=179502961277.2490531.3324622150540616569.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc==?utf-8?b?TmVib2rFoWEgQ3ZldGtvdmnEhyA8bmVia2F0QGdtYWlsLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox