All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: [BlueZ] attrib: Fix smatch "non-ANSI function declaration" warning
Date: Fri, 14 Aug 2026 03:57:33 -0700 (PDT)	[thread overview]
Message-ID: <6a7ef49d.a1accbb4.1a363f.e663@mx.google.com> (raw)
In-Reply-To: <20260814092747.3064311-1-hadess@hadess.net>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      0.36 seconds
GitLint                       FAIL      0.24 seconds
BuildEll                      PASS      17.38 seconds
BluezMake                     PASS      483.22 seconds
MakeCheck                     PASS      0.81 seconds
MakeDistcheck                 PASS      124.51 seconds
CheckValgrind                 PASS      115.91 seconds
CheckSmatch                   WARNING   230.51 seconds
bluezmakeextell               PASS      75.66 seconds
IncrementalBuild              PASS      461.57 seconds
ScanBuild                     PASS      706.53 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ] attrib: Fix smatch "non-ANSI function declaration" warning
WARNING:EMAIL_SUBJECT: A patch subject line should describe the change not the tool that found it
#34: 
Subject: [BlueZ] attrib: Fix smatch "non-ANSI function declaration" warning

/github/workspace/src/patch/14750038.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/patch/14750038.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: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ] attrib: Fix smatch "non-ANSI function declaration" warning

3: B1 Line exceeds max length (95>80): "attrib/interactive.c:175:27: warning: non-ANSI function declaration of function 'disconnect_io'"
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
attrib/interactive.c: note: in included file (through /usr/include/readline/readline.h):attrib/interactive.c:300:23: warning: Variable length array is used.


https://github.com/bluez/bluez/pull/2399

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-08-14 10:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  9:27 [BlueZ] attrib: Fix smatch "non-ANSI function declaration" warning Bastien Nocera
2026-08-14 10:57 ` bluez.test.bot [this message]
2026-08-14 17:20 ` 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=6a7ef49d.a1accbb4.1a363f.e663@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=hadess@hadess.net \
    --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 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.