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: Bluetooth: msft: Fix build when BT_MSFTEXT is not defined
Date: Mon, 27 Sep 2021 16:03:59 -0700 (PDT)	[thread overview]
Message-ID: <61524ddf.1c69fb81.ef9ad.0df6@mx.google.com> (raw)
In-Reply-To: <20210927220024.2776585-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.46 seconds
GitLint                       PASS      0.86 seconds
BuildKernel                   PASS      521.52 seconds
TestRunner: Setup             PASS      385.03 seconds
TestRunner: l2cap-tester      PASS      8.73 seconds
TestRunner: bnep-tester       PASS      4.75 seconds
TestRunner: mgmt-tester       PASS      74.53 seconds
TestRunner: rfcomm-tester     PASS      5.82 seconds
TestRunner: sco-tester        PASS      6.05 seconds
TestRunner: smp-tester        PASS      5.90 seconds
TestRunner: userchan-tester   PASS      5.01 seconds

Details
##############################
Test: CheckPatch - FAIL - 1.46 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: msft: Fix build when BT_MSFTEXT is not defined\WARNING:USE_RELATIVE_PATH: use relative pathname instead of absolute in changelog text
#84: 
/linux/net/bluetooth/msft.h:64: multiple definition of `msft_suspend';

WARNING:USE_RELATIVE_PATH: use relative pathname instead of absolute in changelog text
#87: 
/linux/net/bluetooth/msft.h:64: multiple definition of `msft_resume';

WARNING:USE_RELATIVE_PATH: use relative pathname instead of absolute in changelog text
#90: 
/linux/net/bluetooth/msft.h:64: multiple definition of `msft_suspend';

WARNING:USE_RELATIVE_PATH: use relative pathname instead of absolute in changelog text
#93: 
/linux/net/bluetooth/msft.h:64: multiple definition of `msft_resume';

WARNING:USE_RELATIVE_PATH: use relative pathname instead of absolute in changelog text
#96: 
/linux/net/bluetooth/msft.h:64: multiple definition of `msft_suspend';

WARNING:USE_RELATIVE_PATH: use relative pathname instead of absolute in changelog text
#99: 
/linux/net/bluetooth/msft.h:64: multiple definition of `msft_resume';

total: 0 errors, 6 warnings, 0 checks, 10 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/12521075.patch has style problems, please review.

NOTE: Ignored message types: UNKNOWN_COMMIT_ID

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.




---
Regards,
Linux Bluetooth


[-- Attachment #2: l2cap-tester.log --]
[-- Type: application/octet-stream, Size: 51539 bytes --]

[-- Attachment #3: bnep-tester.log --]
[-- Type: application/octet-stream, Size: 3906 bytes --]

[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 626719 bytes --]

[-- Attachment #5: rfcomm-tester.log --]
[-- Type: application/octet-stream, Size: 14762 bytes --]

[-- Attachment #6: sco-tester.log --]
[-- Type: application/octet-stream, Size: 13924 bytes --]

[-- Attachment #7: smp-tester.log --]
[-- Type: application/octet-stream, Size: 11830 bytes --]

[-- Attachment #8: userchan-tester.log --]
[-- Type: application/octet-stream, Size: 7739 bytes --]

  reply	other threads:[~2021-09-27 23:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 22:00 [PATCH] Bluetooth: msft: Fix build when BT_MSFTEXT is not defined Luiz Augusto von Dentz
2021-09-27 23:03 ` bluez.test.bot [this message]
2021-09-28  8:03 ` Marcel Holtmann

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=61524ddf.1c69fb81.ef9ad.0df6@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).