From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pmenzel@molgen.mpg.de
Subject: RE: [1/2] Revert "Bluetooth: Fix passing NULL to PTR_ERR"
Date: Tue, 08 Feb 2022 15:02:55 -0800 (PST) [thread overview]
Message-ID: <6202f69f.1c69fb81.41e51.a4a9@mx.google.com> (raw)
In-Reply-To: <20220208221911.57058-1-pmenzel@molgen.mpg.de>
[-- Attachment #1: Type: text/plain, Size: 2814 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=612351
---Test result---
Test Summary:
CheckPatch FAIL 2.11 seconds
GitLint FAIL 0.74 seconds
SubjectPrefix PASS 0.51 seconds
BuildKernel PASS 37.46 seconds
BuildKernel32 PASS 33.75 seconds
Incremental Build with patchesPASS 51.88 seconds
TestRunner: Setup PASS 597.35 seconds
TestRunner: l2cap-tester PASS 15.94 seconds
TestRunner: bnep-tester PASS 7.22 seconds
TestRunner: mgmt-tester PASS 128.61 seconds
TestRunner: rfcomm-tester PASS 9.02 seconds
TestRunner: sco-tester PASS 9.47 seconds
TestRunner: smp-tester PASS 9.21 seconds
TestRunner: userchan-tester PASS 7.54 seconds
Details
##############################
Test: CheckPatch - FAIL - 2.11 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[2/2] Revert "Bluetooth: RFCOMM: Replace use of memcpy_from_msg with bt_skb_sendmmsg"\WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#69:
Attempting to send /lib/systemd/systemd to /org/bluez/obex/client/session0
CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#180: FILE: net/bluetooth/rfcomm/sock.c:586:
+ skb = sock_alloc_send_skb(sk, size + RFCOMM_SKB_RESERVE,
+ msg->msg_flags & MSG_DONTWAIT, &err);
total: 0 errors, 1 warnings, 1 checks, 121 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/12739414.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 - 0.74 seconds
Run gitlint with rule in .gitlint
[2/2] Revert "Bluetooth: RFCOMM: Replace use of memcpy_from_msg with bt_skb_sendmmsg"
1: T1 Title exceeds max length (85>80): "[2/2] Revert "Bluetooth: RFCOMM: Replace use of memcpy_from_msg with bt_skb_sendmmsg""
25: B1 Line exceeds max length (95>80): " [CHG] Transfer /org/bluez/obex/client/session0/transfer0 Transferred: 32737 (@32KB/s 00:55)"
31: B1 Line exceeds max length (141>80): "Link: https://lore.kernel.org/linux-bluetooth/aa3ee7ac-6c52-3861-1798-3cc1a37f6ebf@molgen.mpg.de/T/#m1f9673e4ab0d55a7dccf87905337ab2e67d689f1"
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2022-02-08 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 22:19 [PATCH 1/2] Revert "Bluetooth: Fix passing NULL to PTR_ERR" Paul Menzel
2022-02-08 22:19 ` [PATCH 2/2] Revert "Bluetooth: RFCOMM: Replace use of memcpy_from_msg with bt_skb_sendmmsg" Paul Menzel
2022-02-08 23:39 ` Luiz Augusto von Dentz
2022-02-09 1:06 ` Luiz Augusto von Dentz
2022-02-08 23:02 ` 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=6202f69f.1c69fb81.41e51.a4a9@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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).