All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, apusaka@google.com
Subject: RE: [Bluez,v4,1/5] mgmt: Add NAME_REQUEST_FAILED flag for device_found event
Date: Wed, 24 Nov 2021 23:37:11 -0800 (PST)	[thread overview]
Message-ID: <619f3d27.1c69fb81.eee49.61de@mx.google.com> (raw)
In-Reply-To: <20211125150558.Bluez.v4.1.I78857808e0b20c6e4dd934b174d3f1106fe3402d@changeid>

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

---Test result---

Test Summary:
CheckPatch                    PASS      6.86 seconds
GitLint                       FAIL      4.42 seconds
Prep - Setup ELL              PASS      48.93 seconds
Build - Prep                  PASS      0.49 seconds
Build - Configure             PASS      9.03 seconds
Build - Make                  PASS      215.85 seconds
Make Check                    PASS      10.07 seconds
Make Distcheck                PASS      264.17 seconds
Build w/ext ELL - Configure   PASS      9.51 seconds
Build w/ext ELL - Make        PASS      203.22 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
[Bluez,v4,1/5] mgmt: Add NAME_REQUEST_FAILED flag for device_found event
14: B1 Line exceeds max length (121>80): "https://patchwork.kernel.org/project/bluetooth/patch/20211028191805.1.I35b7f3a496f834de6b43a32f94b6160cb1467c94@changeid/"




---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2021-11-25  7:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25  7:06 [Bluez PATCH v4 1/5] mgmt: Add NAME_REQUEST_FAILED flag for device_found event Archie Pusaka
2021-11-25  7:06 ` [Bluez PATCH v4 2/5] Listen and process remote name resolving failure Archie Pusaka
2021-11-25  7:06 ` [Bluez PATCH v4 3/5] device: Save remote name request attempts into cache file Archie Pusaka
2021-11-25  7:06 ` [Bluez PATCH v4 4/5] main: add configurable RemoteNameRequestRetryDelay parameter Archie Pusaka
2021-11-25  7:06 ` [Bluez PATCH v4 5/5] doc: Add Name Request Fail flag in device found event Archie Pusaka
2021-11-25  7:37 ` bluez.test.bot [this message]
2021-11-29 17:49   ` [Bluez,v4,1/5] mgmt: Add NAME_REQUEST_FAILED flag for device_found event Luiz Augusto von Dentz

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=619f3d27.1c69fb81.eee49.61de@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=apusaka@google.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 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.