public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1,1/2] shared/shell: Fix build errors in fc42
Date: Thu, 17 Apr 2025 14:58:54 -0700 (PDT)	[thread overview]
Message-ID: <6801799e.c80a0220.3a5ae2.227c@mx.google.com> (raw)
In-Reply-To: <20250417202113.80496-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PENDING   0.31 seconds
GitLint                       PENDING   0.19 seconds
BuildEll                      PASS      20.42 seconds
BluezMake                     PASS      2654.11 seconds
MakeCheck                     PASS      39.22 seconds
MakeDistcheck                 PASS      198.23 seconds
CheckValgrind                 PASS      280.23 seconds
CheckSmatch                   WARNING   301.86 seconds
bluezmakeextell               PASS      159.08 seconds
IncrementalBuild              PENDING   0.31 seconds
ScanBuild                     PASS      900.12 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/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2025-04-17 21:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 20:21 [PATCH BlueZ v1 1/2] shared/shell: Fix build errors in fc42 Luiz Augusto von Dentz
2025-04-17 20:21 ` [PATCH BlueZ v1 2/2] mesh: Fix build errors when compiling on fc42 Luiz Augusto von Dentz
2025-04-17 21:58 ` bluez.test.bot [this message]
2025-04-18 14:10 ` [PATCH BlueZ v1 1/2] shared/shell: Fix build errors in fc42 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=6801799e.c80a0220.3a5ae2.227c@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox