All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kuba@kernel.org
Subject: RE: [net-next] net: don't include ndisc.h from ipv6.h
Date: Wed, 02 Feb 2022 21:13:00 -0800 (PST)	[thread overview]
Message-ID: <61fb645c.1c69fb81.374cb.75ca@mx.google.com> (raw)
In-Reply-To: <20220203043457.2222388-1-kuba@kernel.org>

[-- 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=610900

---Test result---

Test Summary:
CheckPatch                    PASS      2.97 seconds
GitLint                       PASS      0.99 seconds
SubjectPrefix                 FAIL      0.88 seconds
BuildKernel                   PASS      34.97 seconds
BuildKernel32                 PASS      31.56 seconds
Incremental Build with patchesPASS      44.18 seconds
TestRunner: Setup             PASS      554.52 seconds
TestRunner: l2cap-tester      PASS      15.40 seconds
TestRunner: bnep-tester       PASS      6.96 seconds
TestRunner: mgmt-tester       PASS      116.67 seconds
TestRunner: rfcomm-tester     PASS      8.70 seconds
TestRunner: sco-tester        PASS      8.99 seconds
TestRunner: smp-tester        PASS      8.75 seconds
TestRunner: userchan-tester   PASS      7.12 seconds

Details
##############################
Test: SubjectPrefix - FAIL - 0.88 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2022-02-03  5:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  4:34 [PATCH net-next] net: don't include ndisc.h from ipv6.h Jakub Kicinski
2022-02-03  4:53 ` Jeremy Kerr
2022-02-03  5:13 ` bluez.test.bot [this message]
2022-02-03 15:14 ` Stefan Schmidt
2022-02-03 22:48 ` David Ahern
2022-02-03 23:10   ` Jakub Kicinski

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=61fb645c.1c69fb81.374cb.75ca@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=kuba@kernel.org \
    --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.