linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_zijuhu@quicinc.com
Subject: RE: Bluetooth: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING
Date: Wed, 20 Jul 2022 07:26:31 -0700 (PDT)	[thread overview]
Message-ID: <62d81097.1c69fb81.6dc4a.ee9f@mx.google.com> (raw)
In-Reply-To: <1658326045-9931-2-git-send-email-quic_zijuhu@quicinc.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      4.84 seconds
GitLint                       FAIL      2.87 seconds
SubjectPrefix                 PASS      2.63 seconds
BuildKernel                   PASS      33.91 seconds
BuildKernel32                 PASS      30.29 seconds
Incremental Build with patchesFAIL      39.46 seconds
TestRunner: Setup             PASS      505.54 seconds
TestRunner: l2cap-tester      PASS      17.30 seconds
TestRunner: bnep-tester       PASS      6.03 seconds
TestRunner: mgmt-tester       PASS      99.74 seconds
TestRunner: rfcomm-tester     PASS      9.36 seconds
TestRunner: sco-tester        PASS      9.18 seconds
TestRunner: smp-tester        PASS      9.26 seconds
TestRunner: userchan-tester   PASS      6.18 seconds

Details
##############################
Test: GitLint - FAIL - 2.87 seconds
Run gitlint with rule in .gitlint
[v1,3/3] Bluetooth: btusb: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING for fake CSR
1: T1 Title exceeds max length (82>80): "[v1,3/3] Bluetooth: btusb: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING for fake CSR"


##############################
Test: Incremental Build with patches - FAIL - 39.46 seconds
Incremental build per patch in the series
drivers/bluetooth/btusb.c: In function ‘btusb_setup_csr’:
drivers/bluetooth/btusb.c:2075:11: error: ‘HCI_QUIRK_BROKEN_ERR_DATA_REPORTING’ undeclared (first use in this function); did you mean ‘HCI_OP_READ_DEF_ERR_DATA_REPORTING’?
 2075 |   set_bit(HCI_QUIRK_BROKEN_ERR_DATA_REPORTING, &hdev->quirks);
      |           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |           HCI_OP_READ_DEF_ERR_DATA_REPORTING
drivers/bluetooth/btusb.c:2075:11: note: each undeclared identifier is reported only once for each function it appears in
drivers/bluetooth/btusb.c: In function ‘btusb_setup_qca’:
drivers/bluetooth/btusb.c:3358:10: error: ‘HCI_QUIRK_BROKEN_ERR_DATA_REPORTING’ undeclared (first use in this function); did you mean ‘HCI_OP_READ_DEF_ERR_DATA_REPORTING’?
 3358 |  set_bit(HCI_QUIRK_BROKEN_ERR_DATA_REPORTING, &hdev->quirks);
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |          HCI_OP_READ_DEF_ERR_DATA_REPORTING
make[2]: *** [scripts/Makefile.build:288: drivers/bluetooth/btusb.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [scripts/Makefile.build:550: drivers/bluetooth] Error 2
make: *** [Makefile:1834: drivers] Error 2




---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-07-20 14:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 14:07 [PATCH v1 0/3] Bluetooth: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING Zijun Hu
2022-07-20 14:07 ` [PATCH v1 1/3] Bluetooth: hci_sync: " Zijun Hu
2022-07-20 14:26   ` bluez.test.bot [this message]
2022-07-20 14:07 ` [PATCH v1 2/3] Bluetooth: btusb: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING for QCA Zijun Hu
2022-07-20 14:07 ` [PATCH v1 3/3] Bluetooth: btusb: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING for fake CSR Zijun Hu
2022-07-20 15:38   ` Luiz Augusto von Dentz
2022-07-21  1:28     ` quic_zijuhu
  -- strict thread matches above, loose matches on Subject: below --
2022-07-21  6:04 [PATCH v2 1/4] Bluetooth: hci_sync: Check LMP feature bit instead of quirk Zijun Hu
2022-07-21  7:14 ` Bluetooth: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING 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=62d81097.1c69fb81.6dc4a.ee9f@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=quic_zijuhu@quicinc.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).