From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, lnx.erin@gmail.com
Subject: RE: [net-next,v2] net: Add SO_RCVMARK socket option to provide SO_MARK with recvmsg().
Date: Tue, 26 Apr 2022 21:37:25 -0700 (PDT) [thread overview]
Message-ID: <6268c885.1c69fb81.7b342.59cf@mx.google.com> (raw)
In-Reply-To: <20220427032212.28470-1-lnx.erin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1706 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=636000
---Test result---
Test Summary:
CheckPatch PASS 5.26 seconds
GitLint FAIL 1.08 seconds
SubjectPrefix FAIL 0.96 seconds
BuildKernel PASS 33.03 seconds
BuildKernel32 PASS 29.22 seconds
Incremental Build with patchesPASS 39.41 seconds
TestRunner: Setup PASS 495.09 seconds
TestRunner: l2cap-tester PASS 18.12 seconds
TestRunner: bnep-tester PASS 6.47 seconds
TestRunner: mgmt-tester PASS 105.38 seconds
TestRunner: rfcomm-tester PASS 10.06 seconds
TestRunner: sco-tester PASS 9.79 seconds
TestRunner: smp-tester PASS 9.70 seconds
TestRunner: userchan-tester PASS 6.66 seconds
Details
##############################
Test: GitLint - FAIL - 1.08 seconds
Run gitlint with rule in .gitlint
[net-next,v2] net: Add SO_RCVMARK socket option to provide SO_MARK with recvmsg().
1: T1 Title exceeds max length (82>80): "[net-next,v2] net: Add SO_RCVMARK socket option to provide SO_MARK with recvmsg()."
1: T3 Title has trailing punctuation (.): "[net-next,v2] net: Add SO_RCVMARK socket option to provide SO_MARK with recvmsg()."
##############################
Test: SubjectPrefix - FAIL - 0.96 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-04-27 4:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202204270907.nUUrw3dS-lkp@intel.com>
2022-04-27 3:21 ` [PATCH net-next v2] net: Add SO_RCVMARK socket option to provide SO_MARK with recvmsg() Erin MacNeil
2022-04-27 4:37 ` bluez.test.bot [this message]
2022-04-27 20:02 ` [PATCH net-next v3] net: SO_RCVMARK socket option for " Erin MacNeil
2022-04-27 20:47 ` Eric Dumazet
2022-04-27 21:05 ` [net-next,v3] " bluez.test.bot
2022-04-28 1:27 ` [PATCH net-next v3] " David Ahern
2022-04-28 6:32 ` Marc Kleine-Budde
2022-04-28 21:20 ` patchwork-bot+netdevbpf
2022-04-30 8:00 ` 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=6268c885.1c69fb81.7b342.59cf@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lnx.erin@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