From: SebastianForslund <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 71188e: test-vcp: Fix CCC value endianness
Date: Fri, 08 Dec 2023 07:17:58 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/8980f4-b0656c@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 71188eb0e752d26fe372fd06c20698aea89e3446
https://github.com/bluez/bluez/commit/71188eb0e752d26fe372fd06c20698aea89e3446
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2023-12-06 (Wed, 06 Dec 2023)
Changed paths:
M unit/test-vcp.c
Log Message:
-----------
test-vcp: Fix CCC value endianness
CCC value is 2 octects long so it needs to be converted using
cpu_to_le16 in order to not fail in Big Endian architectures.
Commit: b0656c2cf14da4b43ee7a446bfa9c5f1d3c044b0
https://github.com/bluez/bluez/commit/b0656c2cf14da4b43ee7a446bfa9c5f1d3c044b0
Author: Sebastian Forslund <sebastian.david.forslund@gmail.com>
Date: 2023-12-08 (Fri, 08 Dec 2023)
Changed paths:
M src/shared/ad.c
Log Message:
-----------
Pattern match on service- and manufacturer data
When advertisement monitoring, manufacturer data and service data was
not being matched against. This made it so that advertisement monitoring
with or_patterns did not work that type of data.
We must start matching against the data in the manufacturer_data and
service_data queues. Run a different match-function depending on the
type of monitor that is being matched against.
Closes: https://github.com/bluez/bluez/issues/652
Compare: https://github.com/bluez/bluez/compare/8980f4f1f730...b0656c2cf14d
reply other threads:[~2023-12-08 15:17 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/8980f4-b0656c@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 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).