Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <01a23e10715b0be35dd4efba6a2bb7ab14cb4a4d.camel@gmail.com>
Subject: Re: Bluetooth: Allow to use configure SCO socket codec parameters
From:   Joschi 127 <127.joschi@gmail.com>
To:     Paul Stejskal <paul.stejskal@gmail.com>,
        linux-bluetooth@vger.kernel.org, pali@kernel.org
Date:   Wed, 28 Oct 2020 19:25:41 +0100
In-Reply-To: <0a520235-f1be-2b51-b047-4960f58e0715@gmail.com>
References: <0a520235-f1be-2b51-b047-4960f58e0715@gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk


Am Mittwoch, den 28.10.2020, 11:29 -0500 schrieb Paul Stejskal:
> What can we do to get this published?
> 

As far as I understand Pali is waiting for feedback for his updated
suggestion from this email 
https://lore.kernel.org/linux-bluetooth/20191121224455.orhslaa6zdmlwe43@pali/
 with this patch attached 
https://lore.kernel.org/linux-bluetooth/20191121224455.orhslaa6zdmlwe43@pali/1.2-sco.patch

And as soon as this approach is confirmed I guess he could provide a
new updated patch in the required format and updated to the latest
mainline kernel version?

@Pali: Not sure if I got it right. Maybe you can check yourself and
confirm or correct me if I'm wrong.

Thanks to all!