public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] beecf8: bthost: handle L2CAP_DISCONN_RSP and remove l2cap_...
Date: Sun, 05 Oct 2025 15:26:42 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1008564/000000-a0dda3@github.com> (raw)

  Branch: refs/heads/1008564
  Home:   https://github.com/bluez/bluez
  Commit: beecf8acbff7660f7bef1ea6988e8fa90b98c2d8
      https://github.com/bluez/bluez/commit/beecf8acbff7660f7bef1ea6988e8fa90b98c2d8
  Author: Pauli Virtanen <pav@iki.fi>
  Date:   2025-10-05 (Sun, 05 Oct 2025)

  Changed paths:
    M emulator/bthost.c
    M emulator/bthost.h
    M tools/l2cap-tester.c

  Log Message:
  -----------
  bthost: handle L2CAP_DISCONN_RSP and remove l2cap_conns

Handle L2CAP disconnection response. On receiving disconnection request
or response, remove the associated connection.

Change disconnect handler signature to take also the handle and CID.


  Commit: 711e559d23b11bfa56bd15d6e13c4b036b0cc242
      https://github.com/bluez/bluez/commit/711e559d23b11bfa56bd15d6e13c4b036b0cc242
  Author: Pauli Virtanen <pav@iki.fi>
  Date:   2025-10-05 (Sun, 05 Oct 2025)

  Changed paths:
    M emulator/bthost.c

  Log Message:
  -----------
  bthost: handle L2CAP_FLOW_CONTROL_CREDIT_IND

Parse L2CAP_FLOW_CONTROL_CREDIT_IND and track credits, instead of
sending reject response.  Nothing is done with the credit counts
currently.


  Commit: 95c839b757f40c0db5446f869da53990c971070e
      https://github.com/bluez/bluez/commit/95c839b757f40c0db5446f869da53990c971070e
  Author: Pauli Virtanen <pav@iki.fi>
  Date:   2025-10-05 (Sun, 05 Oct 2025)

  Changed paths:
    M Makefile.tools
    A tools/6lowpan-tester.c

  Log Message:
  -----------
  tools: add 6lowpan-tester

Add 6lowpan smoke testing. It only exercises the kernel 6lowpan L2CAP
connection handling, ipv6 testing is mostly out of scope for the tester.

Add tests:

Basic Framework - Success
Client Connect - Terminate
Client Connect - Disable
Client Connect - Disconnect
Client Recv Dgram - Success
Client Recv Raw - Success


  Commit: a0dda34804c7927708229b3375a6fb37cec765fa
      https://github.com/bluez/bluez/commit/a0dda34804c7927708229b3375a6fb37cec765fa
  Author: Pauli Virtanen <pav@iki.fi>
  Date:   2025-10-05 (Sun, 05 Oct 2025)

  Changed paths:
    M doc/test-runner.rst
    M doc/tester.config

  Log Message:
  -----------
  doc: enable 6lowpan in tester.config and explain in test-runner.rst

Now that there is a 6lowpan-tester, enable requirements in tester
config, and explain what is needed in test-runner.rst


Compare: https://github.com/bluez/bluez/compare/beecf8acbff7%5E...a0dda34804c7

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

                 reply	other threads:[~2025-10-05 22:26 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/1008564/000000-a0dda3@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