[PATCH BlueZ v1] monitor: Make BTSNOOP_PRIORITY_DEBUG the default

[PATCH BlueZ v1] monitor: Make BTSNOOP_PRIORITY_DEBUG the default

[Luiz Augusto von Dentz]

From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

This makes BTSNOOP_PRIORITY_DEBUG the default so it captures debug logs
from the likes of bluetoothd which is very handy when debugging problems
as otherwise the logs have to entered separately making it hard to
figure out the ordering of the messages.
---
 monitor/packet.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/monitor/packet.c b/monitor/packet.c
index 3e5b3f5e1f26..2eb50896b55b 100644
--- a/monitor/packet.c
+++ b/monitor/packet.c
@@ -101,7 +101,7 @@
 #define UNKNOWN_MANUFACTURER 0xffff
 
 static time_t time_offset = ((time_t) -1);
-static int priority_level = BTSNOOP_PRIORITY_INFO;
+static int priority_level = BTSNOOP_PRIORITY_DEBUG;
 static unsigned long filter_mask = 0;
 static bool index_filter = false;
 static uint16_t index_current = 0;
-- 
2.47.1

RE: [BlueZ,v1] monitor: Make BTSNOOP_PRIORITY_DEBUG the default

[bluez.test.bot]

[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]

This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=923084

---Test result---

Test Summary:
CheckPatch                    PENDING   0.31 seconds
GitLint                       PENDING   0.31 seconds
BuildEll                      PASS      20.89 seconds
BluezMake                     PASS      1636.85 seconds
MakeCheck                     PASS      12.99 seconds
MakeDistcheck                 PASS      162.06 seconds
CheckValgrind                 PASS      215.91 seconds
CheckSmatch                   WARNING   274.43 seconds
bluezmakeextell               PASS      99.80 seconds
IncrementalBuild              PENDING   0.36 seconds
ScanBuild                     PASS      860.51 seconds

Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:

##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:

##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/packet.c: note: in included file:monitor/display.h:82:26: warning: Variable length array is used.monitor/packet.c:1868:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/bt.h:3606:52: warning: array of flexible structuresmonitor/bt.h:3594:40: warning: array of flexible structures
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth

Re: [PATCH BlueZ v1] monitor: Make BTSNOOP_PRIORITY_DEBUG the default

[patchwork-bot+bluetooth]

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue,  7 Jan 2025 12:35:42 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> This makes BTSNOOP_PRIORITY_DEBUG the default so it captures debug logs
> from the likes of bluetoothd which is very handy when debugging problems
> as otherwise the logs have to entered separately making it hard to
> figure out the ordering of the messages.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v1] monitor: Make BTSNOOP_PRIORITY_DEBUG the default
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4fa24e6583a3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html