linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, puffy.taco@gmail.com
Subject: RE: LE OOB pairing support
Date: Fri, 10 Jun 2022 17:37:31 -0700 (PDT)	[thread overview]
Message-ID: <62a3e3cb.1c69fb81.6a9f7.023b@mx.google.com> (raw)
In-Reply-To: <20220610221124.18591-2-puffy.taco@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      4.40 seconds
GitLint                       PASS      2.99 seconds
Prep - Setup ELL              PASS      43.55 seconds
Build - Prep                  PASS      0.74 seconds
Build - Configure             PASS      8.77 seconds
Build - Make                  PASS      1434.98 seconds
Make Check                    PASS      11.93 seconds
Make Check w/Valgrind         PASS      450.60 seconds
Make Distcheck                PASS      234.96 seconds
Build w/ext ELL - Configure   PASS      8.77 seconds
Build w/ext ELL - Make        PASS      1408.11 seconds
Incremental Build with patchesPASS      4282.77 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[v2,1/3] eir: parse data types for LE OOB pairing
WARNING:LONG_LINE_COMMENT: line length of 89 exceeds 80 columns
#202: FILE: src/eir.h:40:
+#define EIR_LE_SC_CONF              0x22  /* LE: Secure Connections Confirmation Value */

WARNING:LONG_LINE_COMMENT: line length of 83 exceeds 80 columns
#203: FILE: src/eir.h:41:
+#define EIR_LE_SC_RAND              0x23  /* LE: Secure Connections Random Value */

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

[v2,2/3] Accept LE formatted EIR data with neard plugin
WARNING:LONG_LINE_COMMENT: line length of 89 exceeds 80 columns
#184: FILE: plugins/neard.c:581:
+			/* nokia.com:bt, EIR, and EIR.le should not be passed together */

WARNING:LONG_LINE_COMMENT: line length of 89 exceeds 80 columns
#193: FILE: plugins/neard.c:599:
+			/* nokia.com:bt, EIR, and EIR.le should not be passed together */

WARNING:LONG_LINE_COMMENT: line length of 89 exceeds 80 columns
#206: FILE: plugins/neard.c:617:
+			/* nokia.com:bt, EIR, and EIR.le should not be passed together */

WARNING:LONG_LINE: line length of 85 exceeds 80 columns
#243: FILE: plugins/neard.c:750:
+								remote.address_type);

WARNING:LONG_LINE: line length of 85 exceeds 80 columns
#252: FILE: plugins/neard.c:774:
+							remote.address_type, io_cap);

WARNING:LONG_LINE: line length of 84 exceeds 80 columns
#322: FILE: src/adapter.h:216:
+					const bdaddr_t *bdaddr, uint8_t bdaddr_type,

WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#323: FILE: src/adapter.h:217:
+					uint8_t *hash192, uint8_t *randomizer192,

WARNING:LONG_LINE: line length of 82 exceeds 80 columns
#324: FILE: src/adapter.h:218:
+					uint8_t *hash256, uint8_t *randomizer256);

/github/workspace/src/12878131.patch total: 0 errors, 8 warnings, 206 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/12878131.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-06-11  0:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 22:11 [PATCH v2 0/3] LE OOB pairing support Michael Brudevold
2022-06-10 22:11 ` [PATCH v2 1/3] eir: parse data types for LE OOB pairing Michael Brudevold
2022-06-11  0:37   ` bluez.test.bot [this message]
2022-06-11 20:27   ` Luiz Augusto von Dentz
2022-06-13 21:42     ` Mike Brudevold
2022-06-13 21:55       ` Luiz Augusto von Dentz
2022-06-13 22:28         ` Mike Brudevold
2022-06-21 18:57           ` Luiz Augusto von Dentz
2022-06-21 19:50             ` Mike Brudevold
2022-06-10 22:11 ` [PATCH v2 2/3] Accept LE formatted EIR data with neard plugin Michael Brudevold
2022-06-10 22:11 ` [PATCH v2 3/3] neard: Update D-Bus path and interface Michael Brudevold
  -- strict thread matches above, loose matches on Subject: below --
2022-06-03 22:32 [PATCH 1/3] eir: parse data types for LE OOB pairing Michael Brudevold
2022-06-04  0:52 ` LE OOB pairing support bluez.test.bot

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=62a3e3cb.1c69fb81.6a9f7.023b@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=puffy.taco@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;
as well as URLs for NNTP newsgroup(s).