From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_zijuhu@quicinc.com
Subject: RE: [v1,1/1] Bluetooth: hci_event: Fix wakeup BD_ADDR are wrongly recorded
Date: Tue, 09 Jan 2024 01:32:44 -0800 (PST) [thread overview]
Message-ID: <659d12bc.170a0220.2fccd.5149@mx.google.com> (raw)
In-Reply-To: <1704789450-17754-1-git-send-email-quic_zijuhu@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 1826 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=815323
---Test result---
Test Summary:
CheckPatch PASS 0.50 seconds
GitLint PASS 0.24 seconds
SubjectPrefix PASS 0.09 seconds
BuildKernel PASS 28.04 seconds
CheckAllWarning PASS 30.74 seconds
CheckSparse WARNING 36.92 seconds
CheckSmatch WARNING 99.22 seconds
BuildKernel32 PASS 27.10 seconds
TestRunnerSetup PASS 436.36 seconds
TestRunner_l2cap-tester PASS 22.97 seconds
TestRunner_iso-tester PASS 47.10 seconds
TestRunner_bnep-tester PASS 6.76 seconds
TestRunner_mgmt-tester PASS 163.40 seconds
TestRunner_rfcomm-tester PASS 10.85 seconds
TestRunner_sco-tester PASS 14.37 seconds
TestRunner_ioctl-tester PASS 11.93 seconds
TestRunner_mesh-tester PASS 8.86 seconds
TestRunner_smp-tester PASS 9.68 seconds
TestRunner_userchan-tester PASS 7.27 seconds
IncrementalBuild PASS 25.85 seconds
Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-01-09 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 8:37 [PATCH v1 1/1] Bluetooth: hci_event: Fix wakeup BD_ADDR are wrongly recorded Zijun Hu
2024-01-09 9:32 ` bluez.test.bot [this message]
2024-01-09 9:58 ` Paul Menzel
2024-01-09 10:39 ` quic_zijuhu
2024-01-09 11:03 ` [PATCH v2 1/1] Bluetooth: hci_event: Fix wrongly recorded wakeup BD_ADDR Zijun Hu
2024-01-09 11:30 ` [v2,1/1] " bluez.test.bot
2024-01-09 17:00 ` [PATCH v2 1/1] " patchwork-bot+bluetooth
2024-01-09 17:00 ` [PATCH v1 1/1] Bluetooth: hci_event: Fix wakeup BD_ADDR are wrongly recorded 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=659d12bc.170a0220.2fccd.5149@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).