From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e501c8: shared/shell: Fix build errors in fc42
Date: Fri, 18 Apr 2025 07:13:31 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/aedd7b-2a569e@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: e501c8ab3023155700bc752d318b1ba3480311da
https://github.com/bluez/bluez/commit/e501c8ab3023155700bc752d318b1ba3480311da
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-04-17 (Thu, 17 Apr 2025)
Changed paths:
M src/shared/shell.c
Log Message:
-----------
shared/shell: Fix build errors in fc42
This fixes the following errors:
src/shared/shell.c: In function 'rl_cleanup':
src/shared/shell.c:1429:20: error: zero-length gnu_printf format string [-Werror=format-zero-length]
1429 | rl_message("");
| ^~
Commit: 2a569ec80ffb4ea7a7dc1651b6befb51f2d34cd7
https://github.com/bluez/bluez/commit/2a569ec80ffb4ea7a7dc1651b6befb51f2d34cd7
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-04-17 (Thu, 17 Apr 2025)
Changed paths:
M mesh/crypto.c
M tools/mesh-gatt/crypto.c
Log Message:
-----------
mesh: Fix build errors when compiling on fc42
./mesh/crypto.c: In function ‘mesh_crypto_device_key’:
./mesh/crypto.c:436:33: error: initializer-string for array of ‘unsigned char’ truncates NUL terminator but destination lacks ‘nonstring’ attribute (5 chars into 4 available) [-Werror=unterminated-string-initialization]
436 | const uint8_t prdk[4] = "prdk";
| ^~~~~~
Compare: https://github.com/bluez/bluez/compare/aedd7b936b72...2a569ec80ffb
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-04-18 14:13 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/aedd7b-2a569e@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