From: apusaka <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] b8d42b: test-mesh-crypto: Don't attempt to run test if AF_...
Date: Tue, 26 May 2026 10:39:07 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/f818e9-b49316@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: b8d42b282b3c17f1f4838039fa23ba24f07db723
https://github.com/bluez/bluez/commit/b8d42b282b3c17f1f4838039fa23ba24f07db723
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-05-22 (Fri, 22 May 2026)
Changed paths:
M unit/test-mesh-crypto.c
Log Message:
-----------
test-mesh-crypto: Don't attempt to run test if AF_ALG is not available
This make use of mesh_crypto_check_avail to check if AF_ALG is available
and if not just bail out which is similar to how test-crypto handles
when bt_crypto_new returns NULL.
Commit: b493164ffbff277bdb540f6d779ba4b4645b3679
https://github.com/bluez/bluez/commit/b493164ffbff277bdb540f6d779ba4b4645b3679
Author: Archie Pusaka <apusaka@chromium.org>
Date: 2026-05-26 (Tue, 26 May 2026)
Changed paths:
M monitor/bt.h
M monitor/packet.c
Log Message:
-----------
monitor: Add support for HCI Event Encryption Change v2
> HCI Event: Encryption Change v2 (0x59) plen 5
Status: Success (0x00)
Handle: 256 (BR-ACL) Address: 00:11:22:34:56:78
Encryption: Enabled with E0 (0x01)
Key size: 16
Compare: https://github.com/bluez/bluez/compare/f818e9d0c9df...b493164ffbff
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-05-26 17:39 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/f818e9-b49316@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