From: Christian Eggers <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 7a7878: mesh: crypto: remove dead function declaration
Date: Tue, 08 Jul 2025 06:05:11 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/980052/000000-ae0f45@github.com> (raw)
Branch: refs/heads/980052
Home: https://github.com/bluez/bluez
Commit: 7a7878dea8d3ef872ddf5f49caf9a4ae9871db6c
https://github.com/bluez/bluez/commit/7a7878dea8d3ef872ddf5f49caf9a4ae9871db6c
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-07-08 (Tue, 08 Jul 2025)
Changed paths:
M mesh/crypto.h
Log Message:
-----------
mesh: crypto: remove dead function declaration
The implementation of mesh_aes_ecb_one() has been removed in commit
dfed4839463f ("mesh: Convert crypto to use ELL wrappers").
Commit: ee1b470e458441079660fc7a2725d56d84c9d579
https://github.com/bluez/bluez/commit/ee1b470e458441079660fc7a2725d56d84c9d579
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-07-08 (Tue, 08 Jul 2025)
Changed paths:
M mesh/crypto.c
M mesh/crypto.h
M mesh/net.c
M unit/test-mesh-crypto.c
Log Message:
-----------
mesh: crypto: remove unused function parameter
The 'relay' parameter isn't used by mesh_crypto_packet_build().
Commit: 4f46f3ae455b09dfeaca918abed98f600de70f2b
https://github.com/bluez/bluez/commit/4f46f3ae455b09dfeaca918abed98f600de70f2b
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-07-08 (Tue, 08 Jul 2025)
Changed paths:
M mesh/friend.h
Log Message:
-----------
mesh: friend: remove dead function declarations
The implementations for these functions have been removed in commit
f246d31a7752 ("mesh: Friendship clean-up and rewrite").
Commit: 8cded5bc96e801503cbdf7d441767c8f4e5b3a1d
https://github.com/bluez/bluez/commit/8cded5bc96e801503cbdf7d441767c8f4e5b3a1d
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-07-08 (Tue, 08 Jul 2025)
Changed paths:
M mesh/mesh-config.h
Log Message:
-----------
mesh: mesh-config: remove dead function prototype
mesh_config_write_address() has been added in commit 78668a02d6c4
("mesh: Change mesh_db prefix to mesh_config"), but an implementation
has never existed.
Commit: ae0f45a0679c42a9408142eb9f48f6eb2299ebdd
https://github.com/bluez/bluez/commit/ae0f45a0679c42a9408142eb9f48f6eb2299ebdd
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-07-08 (Tue, 08 Jul 2025)
Changed paths:
M mesh/mesh-io-mgmt.c
Log Message:
-----------
mesh: mesh-io-mgmt: Fix NULL pointer dereference
Don't try to dereference 'pvt' if it's NULL.
Compare: https://github.com/bluez/bluez/compare/7a7878dea8d3%5E...ae0f45a0679c
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-07-08 13:05 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/980052/000000-ae0f45@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