All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: LE Set CIG Parameters / Create CIS fixes
Date: Sun, 28 May 2023 11:37:25 -0700 (PDT)	[thread overview]
Message-ID: <64739f65.050a0220.3c91b.1c77@mx.google.com> (raw)
In-Reply-To: <46eefccceb45556120a0d1fa95cf27c576e9649a.1685294131.git.pav@iki.fi>

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

---Test result---

Test Summary:
CheckPatch                    PASS      5.24 seconds
GitLint                       PASS      1.85 seconds
SubjectPrefix                 PASS      0.61 seconds
BuildKernel                   PASS      37.62 seconds
CheckAllWarning               PASS      40.98 seconds
CheckSparse                   WARNING   46.29 seconds
CheckSmatch                   WARNING   126.89 seconds
BuildKernel32                 PASS      36.43 seconds
TestRunnerSetup               PASS      517.97 seconds
TestRunner_l2cap-tester       PASS      19.01 seconds
TestRunner_iso-tester         PASS      25.59 seconds
TestRunner_bnep-tester        PASS      6.55 seconds
TestRunner_mgmt-tester        PASS      129.05 seconds
TestRunner_rfcomm-tester      PASS      10.34 seconds
TestRunner_sco-tester         PASS      9.55 seconds
TestRunner_ioctl-tester       PASS      11.24 seconds
TestRunner_mesh-tester        PASS      8.29 seconds
TestRunner_smp-tester         PASS      9.34 seconds
TestRunner_userchan-tester    PASS      6.83 seconds
IncrementalBuild              PASS      90.25 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):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):net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):


---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-05-28 18:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-28 17:44 [PATCH 0/6] LE Set CIG Parameters / Create CIS fixes Pauli Virtanen
2023-05-28 17:44 ` [PATCH 1/6] Bluetooth: ISO: fix maximum number of CIS in Set CIG Parameters Pauli Virtanen
2023-05-28 18:37   ` bluez.test.bot [this message]
2023-05-28 23:23   ` Pauli Virtanen
2023-05-28 17:44 ` [PATCH 2/6] Bluetooth: ISO: use hci_sync for setting CIG parameters Pauli Virtanen
2023-05-28 17:44 ` [PATCH 3/6] Bluetooth: ISO: don't try to do Set CIG Parameters if CIG known busy Pauli Virtanen
2023-05-28 17:44 ` [PATCH 4/6] Bluetooth: ISO: don't try to remove CIG if there are bound CIS left Pauli Virtanen
2023-05-28 17:44 ` [PATCH 5/6] Bluetooth: ISO: use correct CIS order in Set CIG Parameters event Pauli Virtanen
2023-05-30 17:46   ` Luiz Augusto von Dentz
2023-05-28 17:44 ` [PATCH 6/6] Bluetooth: ISO: do not emit new LE Create CIS if previous is pending Pauli Virtanen
2023-06-01  6:34 [PATCH v2 1/4] Bluetooth: ISO: use hci_sync for setting CIG parameters Pauli Virtanen
2023-06-01  7:36 ` LE Set CIG Parameters / Create CIS fixes 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=64739f65.050a0220.3c91b.1c77@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pav@iki.fi \
    /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.