All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ceggers@arri.de
Subject: RE: properties_changed: check for NULL iterator
Date: Fri, 23 Sep 2022 08:47:32 -0700 (PDT)	[thread overview]
Message-ID: <632dd514.050a0220.75aa.4c71@mx.google.com> (raw)
In-Reply-To: <20220923145602.25872-2-ceggers@arri.de>

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

---Test result---

Test Summary:
CheckPatch                    PASS      4.24 seconds
GitLint                       FAIL      2.93 seconds
Prep - Setup ELL              PASS      31.70 seconds
Build - Prep                  PASS      0.62 seconds
Build - Configure             PASS      7.06 seconds
Build - Make                  PASS      884.89 seconds
Make Check                    PASS      11.33 seconds
Make Check w/Valgrind         PASS      344.83 seconds
Make Distcheck                PASS      211.00 seconds
Build w/ext ELL - Configure   PASS      7.14 seconds
Build w/ext ELL - Make        PASS      116.89 seconds
Incremental Build w/ patches  PASS      533.39 seconds
Scan Build                    PASS      715.27 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
[BlueZ,v2,4/9] advertising: parse_min_interval: reset min_interval if iter is NULL
1: T1 Title exceeds max length (82>80): "[BlueZ,v2,4/9] advertising: parse_min_interval: reset min_interval if iter is NULL"




---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-09-23 15:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 14:55 [PATCH BlueZ v2 0/9] properties_changed: check for NULL iterator Christian Eggers
2022-09-23 14:55 ` [PATCH BlueZ v2 1/9] advertising: parse_secondary: fix loop condition Christian Eggers
2022-09-23 15:47   ` bluez.test.bot [this message]
2022-09-29 16:49   ` properties_changed: check for NULL iterator bluez.test.bot
2022-09-29 17:45   ` bluez.test.bot
2022-09-29 18:40   ` bluez.test.bot
2022-09-29 19:01   ` bluez.test.bot
2022-09-29 19:29   ` bluez.test.bot
2022-09-29 19:47   ` bluez.test.bot
2022-09-29 20:34   ` bluez.test.bot
2022-09-29 20:53   ` bluez.test.bot
2022-09-29 21:30   ` bluez.test.bot
2022-09-29 21:52   ` bluez.test.bot
2022-09-29 22:32   ` bluez.test.bot
2022-09-29 22:52   ` bluez.test.bot
2022-09-29 23:40   ` bluez.test.bot
2022-09-29 23:59   ` bluez.test.bot
2022-09-23 14:55 ` [PATCH BlueZ v2 2/9] advertising: parse_secondary: fix mask value Christian Eggers
2022-09-23 14:55 ` [PATCH BlueZ v2 3/9] advertising: parse_secondary: check for NULL iterator Christian Eggers
2022-09-23 14:55 ` [PATCH BlueZ v2 4/9] advertising: parse_min_interval: reset min_interval if iter is NULL Christian Eggers
2022-09-23 14:57 ` [PATCH BlueZ v2 5/9] advertising: parse_[min|max]_interval: reset value " Christian Eggers
2022-09-23 14:58 ` [PATCH BlueZ v2 6/9] advertising: parse_tx_power: " Christian Eggers
2022-09-23 14:58   ` [PATCH BlueZ v2 7/9] client/gatt: proxy_property_changed: check for NULL iterator Christian Eggers
2022-09-23 14:58   ` [PATCH BlueZ v2 8/9] gatt: " Christian Eggers
2022-09-23 14:58   ` [PATCH BlueZ v2 9/9] battery: provided_battery_property_changed_cb: check iterator Christian Eggers
2022-09-23 19:18 ` [PATCH BlueZ v2 0/9] properties_changed: check for NULL iterator Luiz Augusto von Dentz
2022-09-23 20:50 ` patchwork-bot+bluetooth
  -- strict thread matches above, loose matches on Subject: below --
2022-09-23 10:24 [PATCH BlueZ 1/9] advertising: parse_secondary: fix loop condition Christian Eggers
2022-09-23 11:21 ` properties_changed: check for NULL iterator 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=632dd514.050a0220.75aa.4c71@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=ceggers@arri.de \
    --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.