From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] eb47cb: monitor/att: Fix not removing read from queue
Date: Fri, 20 May 2022 19:00:25 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/f1069c-bbdd18@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: eb47cb5a04cb1db3b87374c0cda799b7e3ef65af
https://github.com/bluez/bluez/commit/eb47cb5a04cb1db3b87374c0cda799b7e3ef65af
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2022-05-20 (Fri, 20 May 2022)
Changed paths:
M monitor/att.c
Log Message:
-----------
monitor/att: Fix not removing read from queue
The code was using queue_find instead of queue_remove_if so follow up
read wouldn't match the attribute properly.
Commit: 20e944ece7a1d43d2976289c85c19e5ad2056cbd
https://github.com/bluez/bluez/commit/20e944ece7a1d43d2976289c85c19e5ad2056cbd
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2022-05-20 (Fri, 20 May 2022)
Changed paths:
M monitor/att.c
Log Message:
-----------
monitor/att: Fix treating Notification/Indication as a request
Notification/Indication shall be treated as response so the correct
database is used.
Commit: 8e1fd164a7960962235f3757d4e49df7c0229ea0
https://github.com/bluez/bluez/commit/8e1fd164a7960962235f3757d4e49df7c0229ea0
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2022-05-20 (Fri, 20 May 2022)
Changed paths:
M monitor/att.c
Log Message:
-----------
monitor/att: Fix not matching read frame direction
There could be read frames pending on both direction so this ensures
the direction is matched properly.
Commit: bbdd18089b45d99f1e5c34bcc27d69d5b3ecabbf
https://github.com/bluez/bluez/commit/bbdd18089b45d99f1e5c34bcc27d69d5b3ecabbf
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2022-05-20 (Fri, 20 May 2022)
Changed paths:
M monitor/att.c
Log Message:
-----------
monitor/att: Fix parsing of Notify Mutiple
Notify Multiple was parsing handle multiple times causing the length to
be assumed to be a handle.
Compare: https://github.com/bluez/bluez/compare/f1069c4fe106...bbdd18089b45
reply other threads:[~2022-05-21 2:00 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/master/f1069c-bbdd18@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.