From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, silviu.barbulescu@nxp.com
Subject: RE: Add code to support dynamically generated BASE
Date: Fri, 12 Jan 2024 10:17:02 -0800 (PST) [thread overview]
Message-ID: <65a1821e.170a0220.67c21.4b08@mx.google.com> (raw)
In-Reply-To: <20240112165601.134073-2-silviu.barbulescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1536 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=816562
---Test result---
Test Summary:
CheckPatch PASS 0.94 seconds
GitLint FAIL 0.75 seconds
BuildEll PASS 23.78 seconds
BluezMake PASS 699.11 seconds
MakeCheck PASS 12.07 seconds
MakeDistcheck PASS 162.41 seconds
CheckValgrind PASS 224.21 seconds
CheckSmatch PASS 324.51 seconds
bluezmakeextell PASS 105.88 seconds
IncrementalBuild PASS 1312.26 seconds
ScanBuild PASS 957.33 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v2,1/2] shared/bap: Fix dereference of null pointer
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
4: B3 Line contains hard tab characters (\t): "src/shared/bap.c bt_bap_stream_new"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-01-12 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 16:55 [PATCH BlueZ v2 0/2] Add code to support dynamically generated BASE Silviu Florian Barbulescu
2024-01-12 16:56 ` [PATCH BlueZ v2 1/2] shared/bap: Fix dereference of null pointer Silviu Florian Barbulescu
2024-01-12 18:17 ` bluez.test.bot [this message]
2024-01-12 16:56 ` [PATCH BlueZ v2 2/2] shared/bap: Code for dynamically generated BASE Silviu Florian Barbulescu
2024-01-16 15:22 ` Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2024-01-23 12:51 [PATCH BlueZ v4 1/3] shared/bap: Code to generate bcast source BASE Silviu Florian Barbulescu
2024-01-23 14:34 ` Add code to support dynamically generated BASE bluez.test.bot
2024-01-14 22:41 [PATCH v3 1/2] shared/bap: Fix dereference of null pointer Silviu Florian Barbulescu
2024-01-15 0:19 ` Add code to support dynamically generated BASE bluez.test.bot
2024-01-12 14:40 [PATCH BlueZ 1/1] shared/bap: Code for " Silviu Florian Barbulescu
2024-01-12 16:08 ` Add code to 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=65a1821e.170a0220.67c21.4b08@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=silviu.barbulescu@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.