public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [BlueZ,1/4] shared/bap: add bt_bap_stream_config_update for updating QoS choice
Date: Sun, 12 Nov 2023 09:26:01 -0800 (PST)	[thread overview]
Message-ID: <65510aa9.0c0a0220.84fe5.38ae@mx.google.com> (raw)
In-Reply-To: <b48261aeab5a4f5927c9da5296b2ffb079bee375.1699802164.git.pav@iki.fi>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.97 seconds
GitLint                       FAIL      1.46 seconds
BuildEll                      PASS      23.84 seconds
BluezMake                     PASS      544.63 seconds
MakeCheck                     PASS      10.81 seconds
MakeDistcheck                 PASS      146.51 seconds
CheckValgrind                 PASS      207.82 seconds
CheckSmatch                   PASS      311.76 seconds
bluezmakeextell               PASS      95.34 seconds
IncrementalBuild              PASS      1990.39 seconds
ScanBuild                     PASS      886.44 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,2/4] shared/bap: move bcast configure finish out from set_user_data

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
14: B2 Line has trailing whitespace: "    "


---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2023-11-12 17:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12 16:00 [PATCH BlueZ 1/4] shared/bap: add bt_bap_stream_config_update for updating QoS choice Pauli Virtanen
2023-11-12 16:00 ` [PATCH BlueZ 2/4] shared/bap: move bcast configure finish out from set_user_data Pauli Virtanen
2023-11-12 16:00 ` [PATCH BlueZ 3/4] bap: call explicitly bt_bap_stream_bcast_configured when needed Pauli Virtanen
2023-11-12 16:00 ` [PATCH BlueZ 4/4] bap: skip Config Codec when it is not needed Pauli Virtanen
2023-11-12 17:26 ` bluez.test.bot [this message]
2023-11-13 15:39 ` [PATCH BlueZ 1/4] shared/bap: add bt_bap_stream_config_update for updating QoS choice Luiz Augusto von Dentz
2023-11-13 16:27   ` Pauli Virtanen

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=65510aa9.0c0a0220.84fe5.38ae@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pav@iki.fi \
    /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