From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_amisjain@quicinc.com
Subject: RE: [v1] Bluetooth : Update the mas session structure
Date: Mon, 24 Jun 2024 01:44:04 -0700 (PDT) [thread overview]
Message-ID: <667931d4.050a0220.a284f.947b@mx.google.com> (raw)
In-Reply-To: <20240624063627.22705-1-quic_amisjain@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 3024 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=864750
---Test result---
Test Summary:
CheckPatch FAIL 0.64 seconds
GitLint FAIL 0.46 seconds
BuildEll PASS 25.47 seconds
BluezMake PASS 1668.39 seconds
MakeCheck PASS 13.04 seconds
MakeDistcheck PASS 184.98 seconds
CheckValgrind PASS 260.17 seconds
CheckSmatch PASS 369.87 seconds
bluezmakeextell PASS 125.46 seconds
IncrementalBuild PASS 1529.93 seconds
ScanBuild PASS 1098.93 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v1] Bluetooth : Update the mas session structure
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#94:
Update the 'mas_session' structure such that manager_emit_transfer_property(os->service_data, "Size")
WARNING:TYPO_SPELLING: 'tranfer' may be misspelled - perhaps 'transfer'?
#98:
As there is no new tranfer registered during mas connect, hence setting the path to NULL
^^^^^^^
/github/workspace/src/src/13709034.patch total: 0 errors, 2 warnings, 22 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/13709034.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:
[v1] Bluetooth : Update the mas session structure
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
3: B1 Line exceeds max length (101>80): "Update the 'mas_session' structure such that manager_emit_transfer_property(os->service_data, "Size")"
4: B1 Line exceeds max length (104>80): "will get the proper structure in arguments as expected like structure 'obex_transfer' and transfer->path"
7: B1 Line exceeds max length (88>80): "As there is no new tranfer registered during mas connect, hence setting the path to NULL"
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2024-06-24 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 6:36 [PATCH v1] Bluetooth : Update the mas session structure Amisha Jain
2024-06-24 8:44 ` bluez.test.bot [this message]
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=667931d4.050a0220.a284f.947b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=quic_amisjain@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox