From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [1/2] Bluetooth: af_bluetooth: Make BT_PKT_STATUS generic
Date: Thu, 13 Jul 2023 16:37:18 -0700 (PDT) [thread overview]
Message-ID: <64b08aae.c80a0220.c9ada.dac1@mx.google.com> (raw)
In-Reply-To: <20230713224239.2286549-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2021 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=765461
---Test result---
Test Summary:
CheckPatch PASS 2.03 seconds
GitLint PASS 0.66 seconds
SubjectPrefix PASS 0.24 seconds
BuildKernel PASS 33.21 seconds
CheckAllWarning PASS 35.81 seconds
CheckSparse WARNING 40.71 seconds
CheckSmatch WARNING 113.41 seconds
BuildKernel32 PASS 31.61 seconds
TestRunnerSetup PASS 479.01 seconds
TestRunner_l2cap-tester PASS 22.34 seconds
TestRunner_iso-tester PASS 39.90 seconds
TestRunner_bnep-tester PASS 10.06 seconds
TestRunner_mgmt-tester PASS 211.52 seconds
TestRunner_rfcomm-tester PASS 15.32 seconds
TestRunner_sco-tester PASS 16.21 seconds
TestRunner_ioctl-tester PASS 16.96 seconds
TestRunner_mesh-tester PASS 12.55 seconds
TestRunner_smp-tester PASS 13.74 seconds
TestRunner_userchan-tester PASS 10.56 seconds
IncrementalBuild PASS 35.20 seconds
Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/af_bluetooth.c:223:25: warning: context imbalance in 'bt_accept_enqueue' - different lock contexts for basic blocknet/bluetooth/sco.c: note: in included file:./include/net/bluetooth/hci_core.h:150:35: warning: array of flexible structures
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
net/bluetooth/sco.c: note: in included file:./include/net/bluetooth/hci_core.h:150:35: warning: array of flexible structures
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-07-13 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 22:42 [PATCH 1/2] Bluetooth: af_bluetooth: Make BT_PKT_STATUS generic Luiz Augusto von Dentz
2023-07-13 22:42 ` [PATCH 2/2] Bluetooth: ISO: Add support for BT_PKT_STATUS Luiz Augusto von Dentz
2023-07-13 23:37 ` bluez.test.bot [this message]
2023-07-17 20:00 ` [PATCH 1/2] Bluetooth: af_bluetooth: Make BT_PKT_STATUS generic patchwork-bot+bluetooth
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=64b08aae.c80a0220.c9ada.dac1@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).