From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e4f87a: doc: explain SCO BT_SK_PKT_STATUS socket option
Date: Tue, 15 Jul 2025 03:44:37 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/982465/000000-e4f87a@github.com> (raw)
Branch: refs/heads/982465
Home: https://github.com/bluez/bluez
Commit: e4f87a6ef9bbeae64e1586e56e99fd9feb59b250
https://github.com/bluez/bluez/commit/e4f87a6ef9bbeae64e1586e56e99fd9feb59b250
Author: Pauli Virtanen <pav@iki.fi>
Date: 2025-07-15 (Tue, 15 Jul 2025)
Changed paths:
M doc/sco.rst
Log Message:
-----------
doc: explain SCO BT_SK_PKT_STATUS socket option
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-07-15 10:44 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/982465/000000-e4f87a@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