Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, chris.lu@mediatek.com
Subject: RE: Bluetooth: btusb: MediaTek ISO data transmission support
Date: Tue, 28 May 2024 20:56:49 -0700 (PDT)	[thread overview]
Message-ID: <6656a781.050a0220.44b7e.be4a@mx.google.com> (raw)
In-Reply-To: <20240529033038.28458-2-chris.lu@mediatek.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      2.70 seconds
GitLint                       PASS      1.01 seconds
SubjectPrefix                 PASS      0.40 seconds
BuildKernel                   PASS      29.71 seconds
CheckAllWarning               PASS      32.21 seconds
CheckSparse                   WARNING   38.80 seconds
CheckSmatch                   FAIL      34.50 seconds
BuildKernel32                 PASS      28.54 seconds
TestRunnerSetup               PASS      514.87 seconds
TestRunner_l2cap-tester       PASS      18.13 seconds
TestRunner_iso-tester         PASS      28.01 seconds
TestRunner_bnep-tester        PASS      4.73 seconds
TestRunner_mgmt-tester        PASS      106.75 seconds
TestRunner_rfcomm-tester      PASS      7.34 seconds
TestRunner_sco-tester         PASS      14.91 seconds
TestRunner_ioctl-tester       PASS      7.62 seconds
TestRunner_mesh-tester        PASS      9.42 seconds
TestRunner_smp-tester         PASS      6.86 seconds
TestRunner_userchan-tester    PASS      4.92 seconds
IncrementalBuild              PASS      39.11 seconds

Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
drivers/bluetooth/btusb.c:1368:45: warning: incorrect type in assignment (different base types)drivers/bluetooth/btusb.c:1368:45:    expected unsigned short [usertype] expectdrivers/bluetooth/btusb.c:1368:45:    got restricted __le16 [usertype] dlen
##############################
Test: CheckSmatch - FAIL
Desc: Run smatch tool with source
Output:

Segmentation fault (core dumped)
make[4]: *** [scripts/Makefile.build:244: net/bluetooth/hci_core.o] Error 139
make[4]: *** Deleting file 'net/bluetooth/hci_core.o'
make[3]: *** [scripts/Makefile.build:485: net/bluetooth] Error 2
make[2]: *** [scripts/Makefile.build:485: net] Error 2
make[2]: *** Waiting for unfinished jobs....
Segmentation fault (core dumped)
make[4]: *** [scripts/Makefile.build:244: drivers/bluetooth/bcm203x.o] Error 139
make[4]: *** Deleting file 'drivers/bluetooth/bcm203x.o'
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [scripts/Makefile.build:485: drivers/bluetooth] Error 2
make[2]: *** [scripts/Makefile.build:485: drivers] Error 2
make[1]: *** [/github/workspace/src/src/Makefile:1919: .] Error 2
make: *** [Makefile:240: __sub-make] Error 2


---
Regards,
Linux Bluetooth


  reply	other threads:[~2024-05-29  3:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29  3:30 [PATCH 0/3] Bluetooth: btusb: MediaTek ISO data transmission support Chris Lu
2024-05-29  3:30 ` [PATCH 1/3] Bluetooth: net: add hci_iso_hdr function for iso data Chris Lu
2024-05-29  3:56   ` bluez.test.bot [this message]
2024-05-29  3:30 ` [PATCH 2/3] Bluetooth: btmtk: add macro to get/set/clear MediaTek defined flags Chris Lu
2024-05-29  3:30 ` [PATCH 3/3] Bluetooth: btusb: mediatek: add MediaTek ISO data transmission function Chris Lu
2024-05-29 15:21 ` [PATCH 0/3] Bluetooth: btusb: MediaTek ISO data transmission support Luiz Augusto von Dentz
  -- strict thread matches above, loose matches on Subject: below --
2024-05-29  6:29 [PATCH v2 1/3] Bluetooth: net: add hci_iso_hdr function for iso data Chris Lu
2024-05-29  7:00 ` Bluetooth: btusb: MediaTek ISO data transmission support 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=6656a781.050a0220.44b7e.be4a@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=chris.lu@mediatek.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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