From: Rudi Heitbaum <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 998452: client/btpclient: Fix build warning
Date: Tue, 17 Feb 2026 11:34:25 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/feb4ee-450e99@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 99845224fd4aeadd5f2a860f1af804c5f127256e
https://github.com/bluez/bluez/commit/99845224fd4aeadd5f2a860f1af804c5f127256e
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-02-17 (Tue, 17 Feb 2026)
Changed paths:
M client/btpclient/gap.c
Log Message:
-----------
client/btpclient: Fix build warning
client/btpclient/gap.c:2359:3: warning: Value stored to 'reply' is never
read [deadcode.DeadStores]
2359 | reply = l_dbus_message_new_error(ag->pending_req,
| ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2360 | "org.bluez.Error.Rejected",
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~
2361 | "Passkey mismatch");
| ~~~~~~~~~~~~~~~~~~~
1 warning generated.
Commit: 450e99f0801faa22d9a622b8c0d961641b407d2e
https://github.com/bluez/bluez/commit/450e99f0801faa22d9a622b8c0d961641b407d2e
Author: Rudi Heitbaum <rudi@heitbaum.com>
Date: 2026-02-17 (Tue, 17 Feb 2026)
Changed paths:
M src/shared/shell.c
M src/textfile.c
M tools/hciattach_ath3k.c
Log Message:
-----------
src: retain const qualifier from pointer
Since glibc-2.43:
For ISO C23, the functions bsearch, memchr, strchr, strpbrk, strrchr,
strstr, wcschr, wcspbrk, wcsrchr, wcsstr and wmemchr that return
pointers into their input arrays now have definitions as macros that
return a pointer to a const-qualified type when the in put argument
is a pointer to a const-qualified type.
https://lists.gnu.org/archive/html/info-gnu/2026-01/msg00005.html
fixes:
- warning: assignment discards 'const' qualifier from pointer target
type [-Wdiscarded-qualifiers]
Compare: https://github.com/bluez/bluez/compare/feb4ee9dcd4b...450e99f0801f
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-02-17 19:34 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/feb4ee-450e99@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