From: hadess <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 90a490: monitor: Add support for -K/--kernel
Date: Thu, 21 Aug 2025 10:35:28 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/5f38ea-4784f5@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 90a490569cb823c4621fea3d6f85c47ad06d2f2e
https://github.com/bluez/bluez/commit/90a490569cb823c4621fea3d6f85c47ad06d2f2e
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-08-21 (Thu, 21 Aug 2025)
Changed paths:
M monitor/btmon.rst
M monitor/control.c
M monitor/main.c
M monitor/packet.h
Log Message:
-----------
monitor: Add support for -K/--kernel
This adds support for -K/--kernel that open /proc/kmsg and attempts
to print messages starting with 'Kernel:':
> monitor/btmon -K
= Note: Kernel: BNEP (Ethernet Emulation) ver 1.3
= Note: Kernel: BNEP filters: protocol multicast
= Note: Kernel: BNEP socket layer initialized
= Note: Kernel: MGMT ver 1.23
= Note: Kernel: RFCOMM TTY layer initialized
= Note: Kernel: RFCOMM socket layer initialized
= Note: Kernel: RFCOMM ver 1.11
Commit: 4167e89d8fbba56198ae10635182b43106a5faf0
https://github.com/bluez/bluez/commit/4167e89d8fbba56198ae10635182b43106a5faf0
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-08-21 (Thu, 21 Aug 2025)
Changed paths:
M monitor/packet.c
Log Message:
-----------
monitor: Print message if the frame information cannot be found
While processing Number of Packeted Completed event the code attempts to
print the frame information of each frame being acked but if no frame
was sent it didn't print anything, so this changes it to print
:#(frame not found)
Commit: c773fd53c9539eea59c1a037c4fa7db59e1ac115
https://github.com/bluez/bluez/commit/c773fd53c9539eea59c1a037c4fa7db59e1ac115
Author: Bastien Nocera <hadess@hadess.net>
Date: 2025-08-21 (Thu, 21 Aug 2025)
Changed paths:
M profiles/audio/bass.c
Log Message:
-----------
profiles/audio: Fix uninitialized params.subgroup_data warning
profiles/audio/bass.c:923:2: uninit_use_in_call:
Using uninitialized value "params".
Field "params.subgroup_data" is uninitialized when calling "util_iov_append".
Commit: bb14a8b18f9462aade345cb0529957b152b75db9
https://github.com/bluez/bluez/commit/bb14a8b18f9462aade345cb0529957b152b75db9
Author: Bastien Nocera <hadess@hadess.net>
Date: 2025-08-21 (Thu, 21 Aug 2025)
Changed paths:
M tools/l2cap-tester.c
M tools/tester.h
Log Message:
-----------
tools/tester: Fix fd leaks
tools/tester.h:314:3: leaked_handle:
Handle variable "sk" going out of scope leaks the handle.
tools/l2cap-tester.c:1957:4: leaked_handle:
Handle variable "sk" going out of scope leaks the handle.
Commit: 4784f58ff0ecffb4781e161574a67e26a674cbf0
https://github.com/bluez/bluez/commit/4784f58ff0ecffb4781e161574a67e26a674cbf0
Author: Bastien Nocera <hadess@hadess.net>
Date: 2025-08-21 (Thu, 21 Aug 2025)
Changed paths:
M profiles/input/hog.c
M profiles/input/manager.c
Log Message:
-----------
input: Fix incorrect destructors being used
g_key_file_get_string() expects its value to be freed with g_free(), not
free().
Fixes:
profiles/input/manager.c:118:2: leaked_storage:
Variable "uhid_enabled" going out of scope leaks the storage it points to.
profiles/input/hog.c:267:1: leaked_storage:
Variable "uhid_enabled" going out of scope leaks the storage it points to.
Compare: https://github.com/bluez/bluez/compare/5f38ea159ea8...4784f58ff0ec
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-08-21 17:35 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/5f38ea-4784f5@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;
as well as URLs for NNTP newsgroup(s).