From: ValdikSS <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 60476c: doc: sco.rst: BT_PHY is read-only
Date: Wed, 11 Jun 2025 06:20:16 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/970839/000000-60476c@github.com> (raw)
Branch: refs/heads/970839
Home: https://github.com/bluez/bluez
Commit: 60476cbfd54697ff3620ad1d86d5c94fc684bade
https://github.com/bluez/bluez/commit/60476cbfd54697ff3620ad1d86d5c94fc684bade
Author: ValdikSS <iam@valdikss.org.ru>
Date: 2025-06-11 (Wed, 11 Jun 2025)
Changed paths:
M doc/sco.rst
Log Message:
-----------
doc: sco.rst: BT_PHY is read-only
The kernel is missing BT_PHY setsockopt support, as of 6.16-rc1.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-06-11 13:20 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/970839/000000-60476c@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 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.