linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hj.tedd.an@gmail.com
Subject: RE: [BlueZ,1/3] doc/mgmt-api: Update for Add Extended Advertisement Command
Date: Thu, 16 Jun 2022 15:49:10 -0700 (PDT)	[thread overview]
Message-ID: <62abb366.1c69fb81.23d0a.3b86@mx.google.com> (raw)
In-Reply-To: <20220616195803.99346-1-hj.tedd.an@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      3.59 seconds
GitLint                       FAIL      2.34 seconds
Prep - Setup ELL              PASS      51.57 seconds
Build - Prep                  PASS      0.63 seconds
Build - Configure             PASS      10.34 seconds
Build - Make                  PASS      1503.91 seconds
Make Check                    PASS      12.39 seconds
Make Check w/Valgrind         PASS      540.37 seconds
Make Distcheck                PASS      282.70 seconds
Build w/ext ELL - Configure   PASS      10.49 seconds
Build w/ext ELL - Make        PASS      1443.36 seconds
Incremental Build with patchesPASS      4517.59 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ,3/3] tools/btmgmt: Add support Add Ext Adv command
WARNING:PREFER_FALLTHROUGH: Prefer 'fallthrough;' over fallthrough comment
#233: FILE: tools/btmgmt.c:5031:
+			/* fall through */

WARNING:PREFER_FALLTHROUGH: Prefer 'fallthrough;' over fallthrough comment
#405: FILE: tools/btmgmt.c:5203:
+			/* fall through */

/github/workspace/src/12884720.patch total: 0 errors, 2 warnings, 389 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/12884720.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 with rule in .gitlint
Output:
[BlueZ,2/3] monitor: Update flag information for Extended Advertismement
11: B3 Line contains hard tab characters (\t): "	..."
13: B3 Line contains hard tab characters (\t): "	..."




---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2022-06-16 22:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 19:58 [BlueZ PATCH 1/3] doc/mgmt-api: Update for Add Extended Advertisement Command Tedd Ho-Jeong An
2022-06-16 19:58 ` [BlueZ PATCH 2/3] monitor: Update flag information for Extended Advertismement Tedd Ho-Jeong An
2022-06-16 19:58 ` [BlueZ PATCH 3/3] tools/btmgmt: Add support Add Ext Adv command Tedd Ho-Jeong An
2022-06-16 22:49 ` bluez.test.bot [this message]
2022-06-17 21:10 ` [BlueZ PATCH 1/3] doc/mgmt-api: Update for Add Extended Advertisement Command 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=62abb366.1c69fb81.23d0a.3b86@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=hj.tedd.an@gmail.com \
    --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 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).