From: Paul Stejskal <paul.stejskal@gmail.com>
To: 127.joschi@gmail.com, linux-bluetooth@vger.kernel.org, pali@kernel.org
Subject: Re: Bluetooth: Allow to use configure SCO socket codec parameters
Date: Wed, 28 Oct 2020 11:29:37 -0500 [thread overview]
Message-ID: <0a520235-f1be-2b51-b047-4960f58e0715@gmail.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 41 bytes --]
What can we do to get this published?
[-- Attachment #1.1.2: OpenPGP_0x8569226F4392D1C8.asc --]
[-- Type: application/pgp-keys, Size: 671 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next reply other threads:[~2020-10-28 21:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 16:29 Paul Stejskal [this message]
2020-10-28 18:25 ` Bluetooth: Allow to use configure SCO socket codec parameters Joschi 127
-- strict thread matches above, loose matches on Subject: below --
2020-01-04 10:04 HCI Set custom bandwidth for AuriStream SCO codec Marcel Holtmann
2020-02-19 12:09 ` David Heidelberg
2020-04-19 23:49 ` Bluetooth: Allow to use configure SCO socket codec parameters Pali Rohár
2020-04-20 23:54 ` Luiz Augusto von Dentz
2020-04-21 8:53 ` Pali Rohár
2020-05-14 19:49 ` Aleksandar Kostadinov
2020-05-15 22:46 ` Andrew Fuller
2020-05-15 23:08 ` Luiz Augusto von Dentz
2020-05-16 7:50 ` Aleksandar Kostadinov
2020-05-16 7:53 ` Pali Rohár
2020-05-18 16:43 ` Luiz Augusto von Dentz
2020-05-18 16:50 ` Pali Rohár
2020-05-27 12:18 ` Ujjwal Sharma
2020-05-27 15:48 ` Luiz Augusto von Dentz
2020-05-27 16:24 ` Ujjwal Sharma
2020-06-04 20:43 ` Pali Rohár
2020-07-13 16:46 ` Pasi Kärkkäinen
2020-09-29 21:04 ` Pali Rohár
2020-10-26 11:45 ` Joschi 127
2020-10-27 23:45 ` Paul Stejskal
2020-10-28 20:25 ` Joschi 127
2020-11-03 12:10 ` Joschi 127
2020-11-03 12:18 ` Pali Rohár
2020-11-03 12:43 ` Jan-Philipp Litza
2020-11-04 0:37 ` Luiz Augusto von Dentz
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=0a520235-f1be-2b51-b047-4960f58e0715@gmail.com \
--to=paul.stejskal@gmail.com \
--cc=127.joschi@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pali@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).