Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [RFC] Bluetooth: btintel: Check firmware version before download
Date: Mon, 01 Feb 2021 15:19:02 -0800 (PST)	[thread overview]
Message-ID: <60188c66.1c69fb81.9d20.2318@mx.google.com> (raw)
In-Reply-To: <20210201220626.890923-1-luiz.dentz@gmail.com>

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

---Test result---

##############################
    Test: CheckPatch - PASS
    

    ##############################
    Test: CheckGitLint - PASS
    

    ##############################
    Test: CheckBuildK - FAIL
    drivers/bluetooth/hci_intel.c: In function ‘intel_setup’:
drivers/bluetooth/hci_intel.c:738:40: error: passing argument 2 of ‘btintel_download_firmware’ from incompatible pointer type [-Werror=incompatible-pointer-types]
  738 |  err = btintel_download_firmware(hdev, fw, &boot_param);
      |                                        ^~
      |                                        |
      |                                        const struct firmware *
In file included from drivers/bluetooth/hci_intel.c:26:
drivers/bluetooth/btintel.h:166:74: note: expected ‘struct intel_version *’ but argument is of type ‘const struct firmware *’
  166 | int btintel_download_firmware(struct hci_dev *dev, struct intel_version *ver,
      |                                                    ~~~~~~~~~~~~~~~~~~~~~~^~~
drivers/bluetooth/hci_intel.c:738:44: error: passing argument 3 of ‘btintel_download_firmware’ from incompatible pointer type [-Werror=incompatible-pointer-types]
  738 |  err = btintel_download_firmware(hdev, fw, &boot_param);
      |                                            ^~~~~~~~~~~
      |                                            |
      |                                            u32 * {aka unsigned int *}
In file included from drivers/bluetooth/hci_intel.c:26:
drivers/bluetooth/btintel.h:167:33: note: expected ‘const struct firmware *’ but argument is of type ‘u32 *’ {aka ‘unsigned int *’}
  167 |          const struct firmware *fw, u32 *boot_param);
      |          ~~~~~~~~~~~~~~~~~~~~~~~^~
drivers/bluetooth/hci_intel.c:738:8: error: too few arguments to function ‘btintel_download_firmware’
  738 |  err = btintel_download_firmware(hdev, fw, &boot_param);
      |        ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/bluetooth/hci_intel.c:26:
drivers/bluetooth/btintel.h:166:5: note: declared here
  166 | int btintel_download_firmware(struct hci_dev *dev, struct intel_version *ver,
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:279: drivers/bluetooth/hci_intel.o] Error 1
make[1]: *** [scripts/Makefile.build:496: drivers/bluetooth] Error 2
make: *** [Makefile:1805: drivers] Error 2


    ##############################
    Test: CheckTestRunner: Setup - PASS
    

    ##############################
    Test: CheckTestRunner: l2cap-tester - PASS
    Total: 40, Passed: 34 (85.0%), Failed: 0, Not Run: 6

    ##############################
    Test: CheckTestRunner: bnep-tester - PASS
    Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0

    ##############################
    Test: CheckTestRunner: mgmt-tester - PASS
    Total: 416, Passed: 400 (96.2%), Failed: 0, Not Run: 16

    ##############################
    Test: CheckTestRunner: rfcomm-tester - PASS
    Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0

    ##############################
    Test: CheckTestRunner: sco-tester - PASS
    Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0

    ##############################
    Test: CheckTestRunner: smp-tester - PASS
    Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0

    ##############################
    Test: CheckTestRunner: userchan-tester - PASS
    Total: 3, Passed: 3 (100.0%), Failed: 0, Not Run: 0

    

---
Regards,
Linux Bluetooth


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

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

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

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

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

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

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

      parent reply	other threads:[~2021-02-01 23:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 22:06 [RFC] Bluetooth: btintel: Check firmware version before download Luiz Augusto von Dentz
2021-02-01 22:13 ` Luiz Augusto von Dentz
2021-02-01 23:19 ` 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=60188c66.1c69fb81.9d20.2318@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