Linux bluetooth development
 help / color / mirror / Atom feed
From: cochcoder <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] a41d01: l2cap-tester: Check compatible interval preferences
Date: Wed, 14 Oct 2026 23:39:30 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1186110/000000-a41d01@github.com> (raw)

  Branch: refs/heads/1186110
  Home:   https://github.com/bluez/bluez
  Commit: a41d0197bc00c72333f67d2a1fe93d4fcc5e8c18
      https://github.com/bluez/bluez/commit/a41d0197bc00c72333f67d2a1fe93d4fcc5e8c18
  Author: Kyle Pepper <cochcoder@proton.me>
  Date:   2026-10-15 (Thu, 15 Oct 2026)

  Changed paths:
    M tools/l2cap-tester.c

  Log Message:
  -----------
  l2cap-tester: Check compatible interval preferences

Load local connection preferences and check both the peer's L2CAP
response and the resulting HCI Connection Update range. Cover overlap,
fast HID and slow idle fallback, and an exact-range control.

Assisted-by: OpenCode:gpt-6.1-sol



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

                 reply	other threads:[~2026-10-15  6:39 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/1186110/000000-a41d01@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