All of lore.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: [BlueZ,v7,1/8] lib: Add definitions for ISO socket
Date: Wed, 22 Jun 2022 19:48:22 -0700 (PDT)	[thread overview]
Message-ID: <62b3d476.1c69fb81.a6035.cf43@mx.google.com> (raw)
In-Reply-To: <20220622222801.2676431-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      11.43 seconds
GitLint                       PASS      6.04 seconds
Prep - Setup ELL              PASS      39.41 seconds
Build - Prep                  PASS      0.55 seconds
Build - Configure             PASS      7.67 seconds
Build - Make                  PASS      1383.85 seconds
Make Check                    PASS      11.42 seconds
Make Check w/Valgrind         PASS      419.42 seconds
Make Distcheck                PASS      215.01 seconds
Build w/ext ELL - Configure   PASS      7.90 seconds
Build w/ext ELL - Make        PASS      1346.91 seconds
Incremental Build with patchesPASS      11082.79 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ,v7,7/8] tools: Add isotest tool
WARNING:PREFER_FALLTHROUGH: Prefer 'fallthrough;' over fallthrough comment
#1235: FILE: tools/isotest.c:1118:
+		/* fall through */

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


      parent reply	other threads:[~2022-06-23  2:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 22:27 [BlueZ PATCH v7 1/8] lib: Add definitions for ISO socket Luiz Augusto von Dentz
2022-06-22 22:27 ` [BlueZ PATCH v7 2/8] shared/util: Decode BlueZ Experimental ISO Socket UUID Luiz Augusto von Dentz
2022-06-22 22:27 ` [BlueZ PATCH v7 3/8] mgmt-tester: Fix Read Exp Feature tests Luiz Augusto von Dentz
2022-06-22 22:27 ` [BlueZ PATCH v7 4/8] adapter: Add support for setting ISO Socket experimental feature Luiz Augusto von Dentz
2022-06-22 22:27 ` [BlueZ PATCH v7 5/8] btio: Add support for ISO sockets Luiz Augusto von Dentz
2022-06-22 22:27 ` [BlueZ PATCH v7 6/8] tools: Add iso-tester Luiz Augusto von Dentz
2022-06-22 22:28 ` [BlueZ PATCH v7 7/8] tools: Add isotest tool Luiz Augusto von Dentz
2022-06-22 22:28 ` [BlueZ PATCH v7 8/8] isotest: Add documentation Luiz Augusto von Dentz
2022-06-23  2:48 ` bluez.test.bot [this message]

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=62b3d476.1c69fb81.a6035.cf43@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 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.