All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Mohammed Sadiq <sadiq@sadiqpk.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] obexd: Improve handling unsupported MAP events
Date: Mon, 26 Oct 2026 21:40:14 +0000	[thread overview]
Message-ID: <179305081456.3403508.17305582793778128018.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261024115735.2403759-1-sadiq@sadiqpk.org>

Hello:

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

On Sat, 24 Oct 2026 17:27:34 +0530 you wrote:
> As per the spec, unsupported events should be ignored. But since bluez
> used to notify all unsupported events over DBus, removing support for
> those will break DBus API and clients that may be depending on them.
> 
> But all unsupported events are being notified by replacing the
> original message object, as all map event types defaults to
> MAP_ET_NEW_MESSAGE if unsupported - As the event struct is allocated
> with g_new0().
> 
> [...]

Here is the summary with links:
  - [BlueZ] obexd: Improve handling unsupported MAP events
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8a1b156eda8a

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-10-26 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24 11:57 [PATCH BlueZ] obexd: Improve handling unsupported MAP events Mohammed Sadiq
2026-10-24 14:16 ` [BlueZ] " bluez.test.bot
2026-10-26 21:40 ` 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=179305081456.3403508.17305582793778128018.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=sadiq@sadiqpk.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.