From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iam@sung-woo.kim
Subject: RE: Bluetooth: L2CAP: Fix u8 overflow
Date: Fri, 18 Nov 2022 21:29:44 -0800 (PST) [thread overview]
Message-ID: <637869c8.050a0220.768b3.ed2b@mx.google.com> (raw)
In-Reply-To: <20221118200145.1741199-1-iam@sung-woo.kim>
[-- Attachment #1: Type: text/plain, Size: 2468 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=697073
---Test result---
Test Summary:
CheckPatch FAIL 1.01 seconds
GitLint FAIL 0.55 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 34.03 seconds
BuildKernel32 PASS 30.61 seconds
TestRunnerSetup PASS 430.95 seconds
TestRunner_l2cap-tester PASS 16.47 seconds
TestRunner_iso-tester PASS 15.65 seconds
TestRunner_bnep-tester PASS 5.60 seconds
TestRunner_mgmt-tester PASS 109.00 seconds
TestRunner_rfcomm-tester PASS 9.47 seconds
TestRunner_sco-tester PASS 9.09 seconds
TestRunner_ioctl-tester PASS 10.32 seconds
TestRunner_mesh-tester PASS 7.08 seconds
TestRunner_smp-tester PASS 8.73 seconds
TestRunner_userchan-tester PASS 5.91 seconds
IncrementalBuild PASS 31.92 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: L2CAP: Fix u8 overflow
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#83:
= Note: Linux version 6.1.0-rc2 (x86_64) 0.264594
total: 0 errors, 1 warnings, 0 checks, 9 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/13048756.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
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:
Bluetooth: L2CAP: Fix u8 overflow
20: B2 Line has trailing whitespace: " 08 00 01 00 02 01 04 00 01 10 ff ff ............ "
23: B2 Line has trailing whitespace: " 0a 00 01 00 04 01 06 00 40 00 00 00 00 00 ........@..... "
33: B2 Line has trailing whitespace: " 08 00 01 00 04 01 04 00 40 00 00 00 ........@... "
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-11-19 5:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 20:01 [PATCH] Bluetooth: L2CAP: Fix u8 overflow Sungwoo Kim
2022-11-19 3:07 ` bluez.test.bot
2022-11-19 4:36 ` bluez.test.bot
2022-11-19 5:29 ` bluez.test.bot [this message]
2022-11-22 0:50 ` [PATCH] " 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=637869c8.050a0220.768b3.ed2b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=iam@sung-woo.kim \
--cc=linux-bluetooth@vger.kernel.org \
/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