linux-bluetooth.vger.kernel.org archive mirror
 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,v2] emulator: Add support for vendor commands
Date: Tue, 04 Jan 2022 18:21:10 -0800 (PST)	[thread overview]
Message-ID: <61d50096.1c69fb81.3ebbf.15d7@mx.google.com> (raw)
In-Reply-To: <20220104234326.3001935-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.56 seconds
GitLint                       FAIL      1.00 seconds
Prep - Setup ELL              PASS      47.91 seconds
Build - Prep                  PASS      0.64 seconds
Build - Configure             PASS      9.26 seconds
Build - Make                  PASS      1615.44 seconds
Make Check                    PASS      13.15 seconds
Make Distcheck                FAIL      147.40 seconds
Build w/ext ELL - Configure   PASS      10.01 seconds
Build w/ext ELL - Make        PASS      1559.50 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,v2] emulator: Add support for vendor commands
WARNING:PREFER_DEFINED_ATTRIBUTE_MACRO: Prefer __packed over __attribute__((packed))
#297: FILE: monitor/emulator.h:18:
+} __attribute__((packed));

/github/workspace/src/12703916.patch total: 0 errors, 1 warnings, 146 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/12703916.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:
[RFC,BlueZ,v2] emulator: Add support for vendor commands
14: B3 Line contains hard tab characters (\t): "	."$........"


##############################
Test: Make Distcheck - FAIL
Desc: Run distcheck to check the distribution
Output:
../../emulator/btdev.c:37:10: fatal error: monitor/emulator.h: No such file or directory
   37 | #include "monitor/emulator.h"
      |          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [Makefile:8003: emulator/android_android_tester-btdev.o] Error 1
make[1]: *** [Makefile:4302: all] Error 2
make: *** [Makefile:11227: distcheck] Error 1




---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-01-05  2:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 23:43 [RFC BlueZ v2] emulator: Add support for vendor commands Luiz Augusto von Dentz
2022-01-05  2:21 ` bluez.test.bot [this message]
2022-01-07 22:46   ` [RFC,BlueZ,v2] " Luiz Augusto von Dentz

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=61d50096.1c69fb81.3ebbf.15d7@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;
as well as URLs for NNTP newsgroup(s).