From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [BlueZ,v2] shared/bap: fix crash unregistering media endpoint while streaming
Date: Fri, 24 Feb 2023 11:11:12 -0800 (PST) [thread overview]
Message-ID: <63f90bd0.c80a0220.c4fe.02ff@mx.google.com> (raw)
In-Reply-To: <fe1bf6efbd6bdfc8507e13559bb3852b23446f2f.1677261870.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 2570 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=724727
---Test result---
Test Summary:
CheckPatch FAIL 0.96 seconds
GitLint FAIL 0.63 seconds
BuildEll PASS 26.04 seconds
BluezMake PASS 738.47 seconds
MakeCheck PASS 11.00 seconds
MakeDistcheck PASS 146.15 seconds
CheckValgrind PASS 238.35 seconds
CheckSmatch PASS 319.64 seconds
bluezmakeextell PASS 95.26 seconds
IncrementalBuild PASS 597.16 seconds
ScanBuild PASS 935.23 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2] shared/bap: fix crash unregistering media endpoint while streaming
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#68:
#0 0x7f93b12b9388 in __interceptor_free.part.0 (/lib64/libasan.so.8+0xb9388)
/github/workspace/src/src/13151651.patch total: 0 errors, 1 warnings, 36 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/13151651.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,v2] shared/bap: fix crash unregistering media endpoint while streaming
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
40: B2 Line has trailing whitespace: " "
42: B2 Line has trailing whitespace: " "
45: B2 Line has trailing whitespace: " "
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-02-24 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 17:17 [RESEND PATCH BlueZ] shared/bap: fix crash unregistering media endpoint while streaming Pauli Virtanen
2023-02-23 18:40 ` [RESEND,BlueZ] " bluez.test.bot
2023-02-23 20:48 ` [RESEND PATCH BlueZ] " Luiz Augusto von Dentz
2023-02-24 18:09 ` [PATCH BlueZ v2] " Pauli Virtanen
2023-02-24 19:11 ` bluez.test.bot [this message]
2023-02-27 21:40 ` patchwork-bot+bluetooth
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=63f90bd0.c80a0220.c4fe.02ff@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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).