From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, aahringo@redhat.com
Subject: RE: net: 6lowpan: simplify lookup by nhc id
Date: Wed, 27 Apr 2022 20:47:39 -0700 (PDT) [thread overview]
Message-ID: <626a0e5b.1c69fb81.7b667.4f88@mx.google.com> (raw)
In-Reply-To: <20220428030534.3220410-2-aahringo@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1362 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=636426
---Test result---
Test Summary:
CheckPatch PASS 5.77 seconds
GitLint PASS 1.40 seconds
SubjectPrefix FAIL 0.92 seconds
BuildKernel PASS 41.46 seconds
BuildKernel32 PASS 37.48 seconds
Incremental Build with patchesPASS 63.86 seconds
TestRunner: Setup PASS 646.14 seconds
TestRunner: l2cap-tester PASS 20.96 seconds
TestRunner: bnep-tester PASS 7.82 seconds
TestRunner: mgmt-tester PASS 130.76 seconds
TestRunner: rfcomm-tester PASS 12.14 seconds
TestRunner: sco-tester PASS 11.49 seconds
TestRunner: smp-tester PASS 11.45 seconds
TestRunner: userchan-tester PASS 7.68 seconds
Details
##############################
Test: SubjectPrefix - FAIL - 0.92 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-04-28 3:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 3:05 [PATCH bluetooth-next 0/3] net: 6lowpan: simplify lookup by nhc id Alexander Aring
2022-04-28 3:05 ` [PATCH bluetooth-next 1/3] net: 6lowpan: remove const from scalars Alexander Aring
2022-04-28 3:47 ` bluez.test.bot [this message]
2022-05-02 19:36 ` Stefan Schmidt
2022-05-03 7:31 ` Jukka Rissanen
2022-04-28 3:05 ` [PATCH bluetooth-next 2/3] net: 6lowpan: use array for find nhc id Alexander Aring
2022-05-02 19:37 ` Stefan Schmidt
2022-05-03 7:32 ` Jukka Rissanen
2022-04-28 3:05 ` [PATCH bluetooth-next 3/3] net: 6lowpan: constify lowpan_nhc structures Alexander Aring
2022-05-02 19:37 ` Stefan Schmidt
2022-05-03 7:32 ` Jukka Rissanen
2022-06-01 20:28 ` [PATCH bluetooth-next 0/3] net: 6lowpan: simplify lookup by nhc id Stefan Schmidt
2022-06-01 21:48 ` Luiz Augusto von Dentz
2022-06-01 21:56 ` Stefan Schmidt
2022-06-01 21:58 ` Luiz Augusto von Dentz
2022-06-02 15:27 ` Marcel Holtmann
2022-06-02 17:38 ` Stefan Schmidt
2022-06-02 17:41 ` Stefan Schmidt
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=626a0e5b.1c69fb81.7b667.4f88@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=aahringo@redhat.com \
--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 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.