From: Christian Eggers <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] bd6c47: mesh: acceptor: fix endianess issues
Date: Mon, 05 May 2025 06:00:23 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/959619/000000-bd6c47@github.com> (raw)
Branch: refs/heads/959619
Home: https://github.com/bluez/bluez
Commit: bd6c47de3daab92b8d22776b4a5040c39bf8077d
https://github.com/bluez/bluez/commit/bd6c47de3daab92b8d22776b4a5040c39bf8077d
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M mesh/prov-acceptor.c
Log Message:
-----------
mesh: acceptor: fix endianess issues
Members of 'struct mesh_net_prov_caps' are in Over-the-Air order and
must be converted to host order first.
Fixes: 838ddc931263 ("mesh: provisionee: Check prov start parameters")
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-05-05 13: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/959619/000000-bd6c47@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