linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Smirnov <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] a589b0: monitor: Add unknown options decoding for Configur...
Date: Thu, 11 Dec 2025 10:48:52 -0800	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/72757c-a589b0@github.com> (raw)

  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: a589b0d73c41eb007112411c6f630bf253c5d2cd
      https://github.com/bluez/bluez/commit/a589b0d73c41eb007112411c6f630bf253c5d2cd
  Author: Andrey Smirnov <andrew.smirnov@gmail.com>
  Date:   2025-12-11 (Thu, 11 Dec 2025)

  Changed paths:
    M monitor/l2cap.c

  Log Message:
  -----------
  monitor: Add unknown options decoding for Configure Response

Unknown options respose for Configure Respose packet has a different
layout that of unaccepted options, so it needs special code to handle
it.

Before:

> ACL Data RX: Handle 12 flags 0x02 dlen 15
      L2CAP: Configure Response (0x05) ident 2 len 7
        Source CID: 64
        Flags: 0x0000
        Result: Failure - unknown options (0x0003)
        04

After:

> ACL Data RX: Handle 12 flags 0x02 dlen 15
      L2CAP: Configure Response (0x05) ident 3 len 7
        Source CID: 65
        Flags: 0x0000
        Result: Failure - unknown options (0x0003)
        Option: Retransmission and Flow Control (0x04)



To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2025-12-11 18:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bluez/bluez/push/refs/heads/master/72757c-a589b0@github.com \
    --to=noreply@github.com \
    --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;
as well as URLs for NNTP newsgroup(s).