All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pmenzel@molgen.mpg.de
Subject: RE: [BlueZ] obexd: Reference count the phonebook back-end setup and teardown
Date: Thu, 10 Sep 2026 11:22:13 -0700 (PDT)	[thread overview]
Message-ID: <6aa2f555.a94c109a.36b556.e3d3@mx.google.com> (raw)
In-Reply-To: <20260817154810.92634-1-pmenzel@molgen.mpg.de>

[-- Attachment #1: Type: text/plain, Size: 1883 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/series/1147292/

---Test result---

Test Summary:
CheckPatch                    FAIL      0.47 seconds
GitLint                       PASS      0.29 seconds
BuildEll                      PASS      17.93 seconds
BluezMake                     PASS      313.35 seconds
MakeCheck                     PASS      14.04 seconds
MakeDistcheck                 PASS      133.67 seconds
CheckValgrind                 PASS      221.90 seconds
CheckSmatch                   PASS      233.97 seconds
bluezmakeextell               PASS      87.32 seconds
IncrementalBuild              PASS      310.60 seconds
ScanBuild                     PASS      926.02 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ] obexd: Reference count the phonebook back-end setup and teardown
ERROR:INITIALISED_STATIC: do not initialise statics to 0
#202: FILE: obexd/plugins/phonebook.c:21:
+static unsigned int refcount = 0;

/github/workspace/src/patch/14753861.patch total: 1 errors, 0 warnings, 121 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/14753861.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.




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

---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2026-09-10 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 15:48 [PATCH BlueZ] obexd: Reference count the phonebook back-end setup and teardown Paul Menzel
2026-08-17 17:12 ` [BlueZ] " bluez.test.bot
2026-09-10 17:42 ` bluez.test.bot
2026-09-10 18:22 ` bluez.test.bot [this message]
2026-09-10 18:40 ` [PATCH BlueZ] " 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=6aa2f555.a94c109a.36b556.e3d3@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    /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.