All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, inga.stotland@gmail.com
Subject: RE: [BlueZ,1/2] tools/mesh-cfgclient: Prevent storing duplicate models
Date: Thu, 16 Mar 2023 12:31:10 -0700 (PDT)	[thread overview]
Message-ID: <64136e7e.9d0a0220.91df2.19dc@mx.google.com> (raw)
In-Reply-To: <20230316180759.147486-1-inga.stotland@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.91 seconds
GitLint                       PASS      0.57 seconds
BuildEll                      PASS      28.31 seconds
BluezMake                     PASS      886.31 seconds
MakeCheck                     PASS      11.37 seconds
MakeDistcheck                 PASS      155.54 seconds
CheckValgrind                 PASS      263.36 seconds
CheckSmatch                   PASS      336.69 seconds
bluezmakeextell               PASS      100.41 seconds
IncrementalBuild              PASS      1489.30 seconds
ScanBuild                     PASS      1054.85 seconds



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2023-03-16 19:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 18:07 [PATCH BlueZ 1/2] tools/mesh-cfgclient: Prevent storing duplicate models Inga Stotland
2023-03-16 18:07 ` [PATCH BlueZ 2/2] tools/mesh-cfgclient: Auto request own composition data Inga Stotland
2023-03-16 19:31 ` bluez.test.bot [this message]
2023-03-16 20:53 ` [PATCH BlueZ 1/2] tools/mesh-cfgclient: Prevent storing duplicate models Paul Menzel
2023-03-16 21:19   ` Stotland, Inga

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=64136e7e.9d0a0220.91df2.19dc@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=inga.stotland@gmail.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.