From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Archie Pusaka <apusaka@google.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>,
Archie Pusaka <apusaka@chromium.org>
Subject: Re: [Bluez PATCH v1] avdtp: fix delay report valid states
Date: Fri, 27 Mar 2020 13:55:28 -0700 [thread overview]
Message-ID: <CABBYNZKpa96qiHbTgTEZr-pyTNO+G4mdYtj7wyshdJfaZ4_-5Q@mail.gmail.com> (raw)
In-Reply-To: <CAJQfnxENfZnXq4e-kaeKF2ByhJ089JXZumWc9ydBJBWGQgTiGw@mail.gmail.com>
Hi Archie,
On Thu, Mar 26, 2020 at 7:14 PM Archie Pusaka <apusaka@google.com> wrote:
>
> [re-sending as plain text]
> Hi Bluez Maintainers,
>
> Could you take a look at this proposal?
>
> Thank you!
>
>
> On Fri, 20 Mar 2020 at 13:14, Archie Pusaka <apusaka@google.com> wrote:
> >
> > From: Archie Pusaka <apusaka@chromium.org>
> >
> > According to AVDTP specification section 6.19,
> > avdtp_delayreport_cmd could also be received when the state of SEP
> > is open.
> >
> > Therefore, updating to accommodate such condition.
> > ---
> >
> > profiles/audio/avdtp.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/profiles/audio/avdtp.c b/profiles/audio/avdtp.c
> > index 0e075f9ff..4b0e63384 100644
> > --- a/profiles/audio/avdtp.c
> > +++ b/profiles/audio/avdtp.c
> > @@ -1936,6 +1936,7 @@ static gboolean avdtp_delayreport_cmd(struct avdtp *session,
> > stream = sep->stream;
> >
> > if (sep->state != AVDTP_STATE_CONFIGURED &&
> > + sep->state != AVDTP_STATE_OPEN &&
> > sep->state != AVDTP_STATE_STREAMING) {
> > err = AVDTP_BAD_STATE;
> > goto failed;
> > --
> > 2.25.1.696.g5e7596f4ac-goog
> >
Applied, thanks.
--
Luiz Augusto von Dentz
prev parent reply other threads:[~2020-03-27 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 5:14 [Bluez PATCH v1] avdtp: fix delay report valid states Archie Pusaka
2020-03-27 2:14 ` Archie Pusaka
2020-03-27 20:55 ` Luiz Augusto von Dentz [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=CABBYNZKpa96qiHbTgTEZr-pyTNO+G4mdYtj7wyshdJfaZ4_-5Q@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=apusaka@chromium.org \
--cc=apusaka@google.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;
as well as URLs for NNTP newsgroup(s).