From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_tjiang@quicinc.com
Subject: RE: Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC QCA2066
Date: Mon, 24 Jul 2023 06:17:56 -0700 (PDT) [thread overview]
Message-ID: <64be7a04.0c0a0220.85f6.6cf5@mx.google.com> (raw)
In-Reply-To: <20230724123637.2877393-2-quic_tjiang@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 2329 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=768884
---Test result---
Test Summary:
CheckPatch PASS 1.99 seconds
GitLint PASS 0.67 seconds
SubjectPrefix PASS 0.26 seconds
BuildKernel PASS 33.39 seconds
CheckAllWarning PASS 36.54 seconds
CheckSparse PASS 41.91 seconds
CheckSmatch PASS 113.19 seconds
BuildKernel32 PASS 32.66 seconds
TestRunnerSetup PASS 495.10 seconds
TestRunner_l2cap-tester PASS 23.80 seconds
TestRunner_iso-tester PASS 43.10 seconds
TestRunner_bnep-tester PASS 10.67 seconds
TestRunner_mgmt-tester PASS 218.38 seconds
TestRunner_rfcomm-tester PASS 16.28 seconds
TestRunner_sco-tester PASS 17.17 seconds
TestRunner_ioctl-tester PASS 18.17 seconds
TestRunner_mesh-tester PASS 13.56 seconds
TestRunner_smp-tester PASS 14.64 seconds
TestRunner_userchan-tester PASS 11.27 seconds
IncrementalBuild FAIL 24.28 seconds
Details
##############################
Test: IncrementalBuild - FAIL
Desc: Incremental build with the patches in the series
Output:
[v11,1/2] Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC QCA2066
drivers/bluetooth/hci_qca.c: In function ‘qca_setup’:
drivers/bluetooth/hci_qca.c:1767:3: error: ‘soc_name’ undeclared (first use in this function)
1767 | soc_name = "ar300x";
| ^~~~~~~~
drivers/bluetooth/hci_qca.c:1767:3: note: each undeclared identifier is reported only once for each function it appears in
make[4]: *** [scripts/Makefile.build:243: drivers/bluetooth/hci_qca.o] Error 1
make[3]: *** [scripts/Makefile.build:477: drivers/bluetooth] Error 2
make[2]: *** [scripts/Makefile.build:477: drivers] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/github/workspace/src/src/Makefile:2020: .] Error 2
make: *** [Makefile:234: __sub-make] Error 2
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-07-24 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 12:36 [PATCH v11 0/2] Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC QCA2066 Tim Jiang
2023-07-24 12:36 ` [PATCH v11 1/2] " Tim Jiang
2023-07-24 13:17 ` bluez.test.bot [this message]
2023-07-24 12:36 ` [PATCH v11 2/2] " Tim Jiang
-- strict thread matches above, loose matches on Subject: below --
2023-07-26 5:22 [PATCH v12 1/2] " Tim Jiang
2023-07-26 6:00 ` bluez.test.bot
2023-07-27 4:40 [PATCH v13 1/2] Bluetooth: hci_qca: adjust qca btsoc type print expression Tim Jiang
2023-07-27 5:36 ` Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC QCA2066 bluez.test.bot
2023-07-27 8:35 [PATCH v14 1/2] Bluetooth: hci_qca: adjust qca btsoc type print expression Tim Jiang
2023-07-27 9:38 ` Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC QCA2066 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=64be7a04.0c0a0220.85f6.6cf5@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=quic_tjiang@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).