Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, leitao@debian.org
Subject: RE: Bluetooth: convert remaining bluetooth socket families to getsockopt_iter
Date: Tue, 12 May 2026 06:44:55 -0700 (PDT)	[thread overview]
Message-ID: <6a032ed7.050a0220.3ac775.b180@mx.google.com> (raw)
In-Reply-To: <20260512-getsock_three-v2-1-30b7b22ef14c@debian.org>

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

---Test result---

Test Summary:
CheckPatch                    PASS      4.19 seconds
GitLint                       PASS      1.80 seconds
SubjectPrefix                 PASS      0.76 seconds
BuildKernel                   PASS      27.64 seconds
CheckAllWarning               PASS      30.79 seconds
CheckSparse                   PASS      29.76 seconds
BuildKernel32                 PASS      26.88 seconds
TestRunnerSetup               PASS      569.83 seconds
TestRunner_l2cap-tester       PASS      378.12 seconds
TestRunner_iso-tester         PASS      597.45 seconds
TestRunner_bnep-tester        PASS      19.24 seconds
TestRunner_mgmt-tester        PASS      2023.41 seconds
TestRunner_rfcomm-tester      PASS      63.64 seconds
TestRunner_sco-tester         PASS      141.77 seconds
TestRunner_ioctl-tester       PASS      133.80 seconds
TestRunner_mesh-tester        PASS      60.07 seconds
TestRunner_smp-tester         PASS      18.27 seconds
TestRunner_userchan-tester    PASS      19.60 seconds
TestRunner_6lowpan-tester     PASS      51.45 seconds
IncrementalBuild              PASS      35.29 seconds



https://github.com/bluez/bluetooth-next/pull/178

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-05-12 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 11:12 [PATCH net-next v2 0/6] Bluetooth: convert remaining bluetooth socket families to getsockopt_iter Breno Leitao
2026-05-12 11:12 ` [PATCH net-next v2 1/6] Bluetooth: hci_sock: write the full optval for getsockopt Breno Leitao
2026-05-12 13:44   ` bluez.test.bot [this message]
2026-05-12 11:12 ` [PATCH net-next v2 2/6] Bluetooth: hci_sock: convert to getsockopt_iter Breno Leitao
2026-05-12 11:12 ` [PATCH net-next v2 3/6] Bluetooth: ISO: " Breno Leitao
2026-05-12 11:12 ` [PATCH net-next v2 4/6] Bluetooth: RFCOMM: " Breno Leitao
2026-05-12 11:12 ` [PATCH net-next v2 5/6] Bluetooth: L2CAP: " Breno Leitao
2026-05-12 11:12 ` [PATCH net-next v2 6/6] Bluetooth: SCO: " Breno Leitao
2026-05-12 17:50 ` [PATCH net-next v2 0/6] Bluetooth: convert remaining bluetooth socket families " patchwork-bot+bluetooth

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=6a032ed7.050a0220.3ac775.b180@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=leitao@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox