From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, claudia.rosu@nxp.com
Subject: RE: Bluetooth: ISO: Copy BASE if service data matches EIR_BAA_SERVICE_UUID
Date: Wed, 06 Sep 2023 03:41:00 -0700 (PDT) [thread overview]
Message-ID: <64f8573c.0c0a0220.5356.18d1@mx.google.com> (raw)
In-Reply-To: <20230906093305.11237-2-claudia.rosu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2170 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=781929
---Test result---
Test Summary:
CheckPatch PASS 0.90 seconds
GitLint FAIL 0.62 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 40.41 seconds
CheckAllWarning PASS 44.74 seconds
CheckSparse WARNING 49.64 seconds
CheckSmatch PASS 133.86 seconds
BuildKernel32 PASS 38.81 seconds
TestRunnerSetup PASS 567.33 seconds
TestRunner_l2cap-tester PASS 29.57 seconds
TestRunner_iso-tester PASS 53.80 seconds
TestRunner_bnep-tester PASS 11.43 seconds
TestRunner_mgmt-tester PASS 233.86 seconds
TestRunner_rfcomm-tester PASS 17.39 seconds
TestRunner_sco-tester PASS 21.31 seconds
TestRunner_ioctl-tester PASS 19.66 seconds
TestRunner_mesh-tester PASS 14.77 seconds
TestRunner_smp-tester PASS 15.49 seconds
TestRunner_userchan-tester PASS 12.22 seconds
IncrementalBuild PASS 31.29 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[1/1] Bluetooth: ISO: Copy BASE if service data matches EIR_BAA_SERVICE_UUID
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
5: B2 Line has trailing whitespace: " "
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/iso.c:1466:18: warning: dereference of noderef expression
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-09-06 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 9:33 [PATCH 0/1] Bluetooth: ISO: Copy BASE if service data matches EIR_BAA_SERVICE_UUID Claudia Draghicescu
2023-09-06 9:33 ` [PATCH 1/1] " Claudia Draghicescu
2023-09-06 10:41 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-07 5:47 [PATCH v2 " Claudia Draghicescu
2023-09-07 16:43 ` bluez.test.bot
2023-09-28 8:02 [PATCH v3 1/1] " Claudia Draghicescu
2023-09-28 8:44 ` 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=64f8573c.0c0a0220.5356.18d1@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=claudia.rosu@nxp.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;
as well as URLs for NNTP newsgroup(s).