From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/5] shared/att: Fix not requeueing in the same channel
Date: Thu, 08 Dec 2022 20:33:59 -0800 (PST) [thread overview]
Message-ID: <6392bab7.4a0a0220.1d0d9.0515@mx.google.com> (raw)
In-Reply-To: <20221209010314.707606-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1858 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=703146
---Test result---
Test Summary:
CheckPatch FAIL 2.52 seconds
GitLint PASS 1.41 seconds
BuildEll PASS 27.40 seconds
BluezMake PASS 1009.44 seconds
MakeCheck PASS 11.49 seconds
MakeDistcheck PASS 149.64 seconds
CheckValgrind PASS 248.26 seconds
bluezmakeextell PASS 97.45 seconds
IncrementalBuild PASS 4456.90 seconds
ScanBuild PASS 1048.52 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,3/5] shared/bap: Read PAC Sink/Source if respective location is found
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#86:
means an error must have occured so this attempt to read the records
^^^^^^^
/github/workspace/src/src/13069110.patch total: 0 errors, 1 warnings, 158 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/13069110.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.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-12-09 4:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 1:03 [PATCH BlueZ 1/5] shared/att: Fix not requeueing in the same channel Luiz Augusto von Dentz
2022-12-09 1:03 ` [PATCH BlueZ 2/5] shared/bap: Log error message if request cannot be sent Luiz Augusto von Dentz
2022-12-09 1:03 ` [PATCH BlueZ 3/5] shared/bap: Read PAC Sink/Source if respective location is found Luiz Augusto von Dentz
2022-12-09 1:03 ` [PATCH BlueZ 4/5] shared/gatt-db: Allow passing NULL to gatt_db_attribute_write Luiz Augusto von Dentz
2022-12-09 1:03 ` [PATCH BlueZ 5/5] shared/bap: Make bt_bap_pac_register to be per session Luiz Augusto von Dentz
2022-12-09 4:33 ` bluez.test.bot [this message]
2022-12-09 21:30 ` [PATCH BlueZ 1/5] shared/att: Fix not requeueing in the same channel 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=6392bab7.4a0a0220.1d0d9.0515@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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