From: Sonny Sasaka <sonnysasaka@chromium.org>
To: Marijn Suijten <marijn.suijten@somainline.org>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ] Queue SetAbsoluteVolume if there is an in-progress one.
Date: Mon, 9 Aug 2021 13:49:02 -0700 [thread overview]
Message-ID: <CAO271m=hQV8ooxAtL0iFO2A1Nw92cq=1DiciivDRJtiN_CHf9Q@mail.gmail.com> (raw)
In-Reply-To: <656381df-01bb-ecdb-a782-79bd8bd05423@somainline.org>
Hi Marijn,
On Mon, Aug 9, 2021 at 1:31 PM Marijn Suijten
<marijn.suijten@somainline.org> wrote:
>
> Hi Sonny,
>
> On 8/9/21 7:46 PM, Sonny Sasaka wrote:
> > Hi Marijn,
> >
> > Thank you for following up. Chrome OS has temporarily adopted my patch
> > to resolve the issue without changing the audio client. We will pick
> > up your patch at the next uprev.
>
> Note that these patches are still draft in search for initial feedback
> on the approach, even if the implementation itself is trivial. Does
> this mean you won't be able to test this locally until the next uprev?
> Either way I will have to confirm their usefulness in PulseAudio too
> before actually committing to this, so there's no hurry.
Yes, Chrome OS is currently not working on solving this issue since
there is already a local fix. We will adopt the BlueZ fix after your
patch gets merged and is available in BlueZ future version when we
rebase with upstream in the next uprev.
>
> Marijn
prev parent reply other threads:[~2021-08-09 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 18:46 [PATCH BlueZ] Queue SetAbsoluteVolume if there is an in-progress one Sonny Sasaka
2021-06-07 20:15 ` [BlueZ] " bluez.test.bot
2021-06-07 21:16 ` [PATCH BlueZ] " Luiz Augusto von Dentz
2021-06-07 22:46 ` Marijn Suijten
2021-06-07 23:47 ` Luiz Augusto von Dentz
2021-06-08 9:50 ` Marijn Suijten
2021-06-08 18:37 ` Sonny Sasaka
2021-08-08 10:15 ` Marijn Suijten
2021-08-09 17:46 ` Sonny Sasaka
2021-08-09 20:31 ` Marijn Suijten
2021-08-09 20:49 ` Sonny Sasaka [this message]
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='CAO271m=hQV8ooxAtL0iFO2A1Nw92cq=1DiciivDRJtiN_CHf9Q@mail.gmail.com' \
--to=sonnysasaka@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marijn.suijten@somainline.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).