From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, lnx.erin@gmail.com
Subject: RE: [net-next,v3] net: SO_RCVMARK socket option for SO_MARK with recvmsg()
Date: Wed, 27 Apr 2022 14:05:59 -0700 (PDT) [thread overview]
Message-ID: <6269b037.1c69fb81.fee4.0f76@mx.google.com> (raw)
In-Reply-To: <20220427200259.2564-1-lnx.erin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1267 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=636346
---Test result---
Test Summary:
CheckPatch PASS 5.22 seconds
GitLint PASS 1.07 seconds
SubjectPrefix FAIL 0.90 seconds
BuildKernel PASS 31.48 seconds
BuildKernel32 PASS 27.89 seconds
Incremental Build with patchesPASS 38.28 seconds
TestRunner: Setup PASS 470.72 seconds
TestRunner: l2cap-tester PASS 17.48 seconds
TestRunner: bnep-tester PASS 6.24 seconds
TestRunner: mgmt-tester PASS 101.20 seconds
TestRunner: rfcomm-tester PASS 9.74 seconds
TestRunner: sco-tester PASS 9.47 seconds
TestRunner: smp-tester PASS 9.56 seconds
TestRunner: userchan-tester PASS 6.38 seconds
Details
##############################
Test: SubjectPrefix - FAIL - 0.90 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 21:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 17:38 [PATCH net-next] net: Add SO_RCVMARK socket option to provide SO_MARK with recvmsg() Erin MacNeil
2022-04-27 1:43 ` kernel test robot
2022-04-27 3:21 ` [PATCH net-next v2] " Erin MacNeil
2022-04-27 3:21 ` Erin MacNeil
2022-04-27 4:37 ` [net-next,v2] " bluez.test.bot
2022-04-27 20:02 ` [PATCH net-next v3] net: SO_RCVMARK socket option for " Erin MacNeil
2022-04-27 20:02 ` Erin MacNeil
2022-04-27 20:47 ` Eric Dumazet
2022-04-27 20:47 ` Eric Dumazet
2022-04-27 21:05 ` bluez.test.bot [this message]
2022-04-28 1:27 ` David Ahern
2022-04-28 1:27 ` David Ahern
2022-04-28 6:32 ` Marc Kleine-Budde
2022-04-28 6:32 ` Marc Kleine-Budde
2022-04-28 21:20 ` patchwork-bot+netdevbpf
2022-04-28 21:20 ` patchwork-bot+netdevbpf
2022-04-30 8:00 ` patchwork-bot+bluetooth
2022-04-30 8:00 ` patchwork-bot+bluetooth
2022-04-27 3:25 ` [PATCH net-next] net: Add SO_RCVMARK socket option to provide " kernel test robot
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=6269b037.1c69fb81.fee4.0f76@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.