All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: Bluetooth: Split bt_iso_qos into dedicated structures
Date: Fri, 31 Mar 2023 09:35:57 -0700 (PDT)	[thread overview]
Message-ID: <64270bed.a70a0220.e894a.4b70@mx.google.com> (raw)
In-Reply-To: <20230331153801.35290-2-iulia.tanasescu@nxp.com>

[-- Attachment #1: Type: text/plain, Size: 1824 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=735874

---Test result---

Test Summary:
CheckPatch                    PASS      1.61 seconds
GitLint                       PASS      0.24 seconds
SubjectPrefix                 PASS      0.07 seconds
BuildKernel                   PASS      35.28 seconds
CheckAllWarning               PASS      37.88 seconds
CheckSparse                   WARNING   42.58 seconds
CheckSmatch                   WARNING   116.58 seconds
BuildKernel32                 PASS      33.78 seconds
TestRunnerSetup               PASS      479.35 seconds
TestRunner_l2cap-tester       PASS      17.18 seconds
TestRunner_iso-tester         PASS      17.30 seconds
TestRunner_bnep-tester        PASS      5.71 seconds
TestRunner_mgmt-tester        PASS      116.12 seconds
TestRunner_rfcomm-tester      PASS      9.00 seconds
TestRunner_sco-tester         PASS      8.30 seconds
TestRunner_ioctl-tester       PASS      9.48 seconds
TestRunner_mesh-tester        PASS      7.38 seconds
TestRunner_smp-tester         PASS      8.22 seconds
TestRunner_userchan-tester    PASS      5.96 seconds
IncrementalBuild              PASS      31.74 seconds

Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):


---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-03-31 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 15:38 [PATCH v3 0/1] Bluetooth: Split bt_iso_qos into dedicated structures Iulia Tanasescu
2023-03-31 15:38 ` [PATCH v3 1/1] " Iulia Tanasescu
2023-03-31 16:35   ` bluez.test.bot [this message]
2023-03-31 22:10 ` [PATCH v3 0/1] " patchwork-bot+bluetooth
  -- strict thread matches above, loose matches on Subject: below --
2023-03-28  7:25 [PATCH v2 1/1] " Iulia Tanasescu
2023-03-28  8:03 ` bluez.test.bot

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=64270bed.a70a0220.e894a.4b70@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=iulia.tanasescu@nxp.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.