From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, nitin.jadhav@nxp.com
Subject: RE: Fixed the crash observed with VOCS
Date: Tue, 25 Jul 2023 06:33:00 -0700 (PDT) [thread overview]
Message-ID: <64bfcf0c.170a0220.504b.136b@mx.google.com> (raw)
In-Reply-To: <20230725112126.49656-2-nitin.jadhav@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2583 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=769262
---Test result---
Test Summary:
CheckPatch FAIL 1.47 seconds
GitLint FAIL 1.02 seconds
BuildEll PASS 34.62 seconds
BluezMake PASS 1221.61 seconds
MakeCheck PASS 13.02 seconds
MakeDistcheck PASS 200.94 seconds
CheckValgrind PASS 327.52 seconds
CheckSmatch PASS 460.63 seconds
bluezmakeextell PASS 134.82 seconds
IncrementalBuild PASS 3132.74 seconds
ScanBuild PASS 1394.25 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v3,2/3] shared/vcp: Fixed issues related to read audio location and descriptor
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#99:
- Audio output descriptor & location read functions, requires code correction
/github/workspace/src/src/13326329.patch total: 0 errors, 1 warnings, 76 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/src/13326329.patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v3,2/3] shared/vcp: Fixed issues related to read audio location and descriptor
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
1: T1 Title exceeds max length (85>80): "[BlueZ,v3,2/3] shared/vcp: Fixed issues related to read audio location and descriptor"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-07-25 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 11:21 [PATCH BlueZ v3 0/3] Fixed the crash observed with VOCS Nitin Jadhav
2023-07-25 11:21 ` [PATCH BlueZ v3 1/3] shared/vcp: " Nitin Jadhav
2023-07-25 13:33 ` bluez.test.bot [this message]
2023-07-25 11:21 ` [PATCH BlueZ v3 2/3] shared/vcp: Fixed issues related to read audio location and descriptor Nitin Jadhav
2023-07-25 11:21 ` [PATCH BlueZ v3 3/3] shared/vcp: Corrected handle size to accommodate included service Nitin Jadhav
2023-07-25 11:46 ` Paul Menzel
2023-07-25 19:50 ` [PATCH BlueZ v3 0/3] Fixed the crash observed with VOCS patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2023-07-24 12:29 [PATCH BlueZ v2 1/1] shared/vcp: " Nitin Jadhav
2023-07-24 14:04 ` bluez.test.bot
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=64bfcf0c.170a0220.504b.136b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=nitin.jadhav@nxp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.