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: [RFC,BlueZ] adapter: Introduce BTD_ADAPTER_DBG
Date: Wed, 23 Mar 2022 15:31:09 -0700 (PDT)	[thread overview]
Message-ID: <623b9fad.1c69fb81.4240f.2b15@mx.google.com> (raw)
In-Reply-To: <20220323205227.3605495-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      0.69 seconds
GitLint                       PASS      0.46 seconds
Prep - Setup ELL              PASS      49.83 seconds
Build - Prep                  PASS      0.62 seconds
Build - Configure             PASS      9.65 seconds
Build - Make                  PASS      1651.60 seconds
Make Check                    PASS      13.21 seconds
Make Check w/Valgrind         PASS      525.62 seconds
Make Distcheck                PASS      270.47 seconds
Build w/ext ELL - Configure   PASS      9.85 seconds
Build w/ext ELL - Make        PASS      1716.04 seconds
Incremental Build with patchesPASS      0.00 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[RFC,BlueZ] adapter: Introduce BTD_ADAPTER_DBG
ERROR:SPACING: space prohibited before that ',' (ctx:WxW)
#99: FILE: src/adapter.h:28:
+							__func__ , ## arg)
 							         ^

ERROR:SPACING: space prohibited before that ',' (ctx:WxW)
#114: FILE: src/device.h:16:
+							__func__ , ## arg)
 							         ^

/github/workspace/src/12790144.patch total: 2 errors, 0 warnings, 20 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/12790144.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.




---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-03-23 22:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 20:52 [RFC BlueZ] adapter: Introduce BTD_ADAPTER_DBG Luiz Augusto von Dentz
2022-03-23 22:31 ` bluez.test.bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-23 22:39 Luiz Augusto von Dentz
2022-03-24  2:49 ` [RFC,BlueZ] " bluez.test.bot
2022-03-24 19:50 ` [RFC 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=623b9fad.1c69fb81.4240f.2b15@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