linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v3,1/4] client/player: Add support for Metadata in BAP Profile
Date: Mon, 01 May 2023 18:32:07 -0700 (PDT)	[thread overview]
Message-ID: <64506817.620a0220.1bf91.dbfc@mx.google.com> (raw)
In-Reply-To: <20230501224410.1119023-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      2.24 seconds
GitLint                       PASS      1.13 seconds
BuildEll                      PASS      37.12 seconds
BluezMake                     PASS      1257.00 seconds
MakeCheck                     PASS      13.05 seconds
MakeDistcheck                 PASS      204.41 seconds
CheckValgrind                 PASS      328.74 seconds
CheckSmatch                   WARNING   455.54 seconds
bluezmakeextell               PASS      137.58 seconds
IncrementalBuild              PASS      4310.09 seconds
ScanBuild                     PASS      1440.05 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v3,4/4] shared/shell: Fix smatch warning
WARNING:EMAIL_SUBJECT: A patch subject line should describe the change not the tool that found it
#72: 
Subject: [BlueZ PATCH v3 4/4] shared/shell: Fix smatch warning

/github/workspace/src/src/13228364.patch total: 0 errors, 1 warnings, 8 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

/github/workspace/src/src/13228364.patch has style problems, please review.

NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.


##############################
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):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):


---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2023-05-02  1:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01 22:44 [BlueZ PATCH v3 1/4] client/player: Add support for Metadata in BAP Profile Luiz Augusto von Dentz
2023-05-01 22:44 ` [BlueZ PATCH v3 2/4] client/player: Fix crash when RegisterEndpoint fails Luiz Augusto von Dentz
2023-05-01 22:44 ` [BlueZ PATCH v3 3/4] shared/shell: Fix not releasing prompt Luiz Augusto von Dentz
2023-05-01 22:44 ` [BlueZ PATCH v3 4/4] shared/shell: Fix smatch warning Luiz Augusto von Dentz
2023-05-02  1:32 ` bluez.test.bot [this message]
2023-05-02 16:40 ` [BlueZ PATCH v3 1/4] client/player: Add support for Metadata in BAP Profile 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=64506817.620a0220.1bf91.dbfc@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;
as well as URLs for NNTP newsgroup(s).