All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ye.he@amlogic.com
Subject: RE: [bluez,v3] bearer: Implement Connect/Disconnect methods
Date: Tue, 18 Nov 2025 02:23:11 -0800 (PST)	[thread overview]
Message-ID: <691c490f.050a0220.e3f29.9b6e@mx.google.com> (raw)
In-Reply-To: <20251118-bearer-impl-v3-1-dadcd8b0c75d@amlogic.com>

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

---Test result---

Test Summary:
CheckPatch                    PENDING   0.33 seconds
GitLint                       PENDING   0.34 seconds
BuildEll                      PASS      20.13 seconds
BluezMake                     PASS      628.69 seconds
MakeCheck                     PASS      21.57 seconds
MakeDistcheck                 PASS      244.27 seconds
CheckValgrind                 PASS      307.33 seconds
CheckSmatch                   WARNING   362.04 seconds
bluezmakeextell               PASS      184.85 seconds
IncrementalBuild              PENDING   0.29 seconds
ScanBuild                     PASS      986.43 seconds

Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:

##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:

##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/bearer.c: note: in included file:src/device.h:244:61: warning: no newline at end of filesrc/device.c:8180:1: warning: no newline at end of filesrc/device.c: note: in included file:src/device.h:244:61: warning: no newline at end of file
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth


  reply	other threads:[~2025-11-18 10:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18  9:29 [PATCH bluez v3] bearer: Implement Connect/Disconnect methods Ye He
2025-11-18  9:29 ` Ye He via B4 Relay
2025-11-18 10:23 ` bluez.test.bot [this message]
2025-11-18 14:14 ` Luiz Augusto von Dentz
2025-11-19  3:26   ` Ye He
     [not found]   ` <09087c54-4d27-460e-a6cb-ac74833068b6@amlogic.com>
2025-11-20 16:22     ` Luiz Augusto von Dentz
2025-11-21  1:59       ` Ye He
2025-11-20 16:24     ` Luiz Augusto von Dentz

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=691c490f.050a0220.e3f29.9b6e@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ye.he@amlogic.com \
    /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.