linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_amisjain@quicinc.com
Subject: RE: [BlueZ,v5] obex: Move size emit signal to plugins instead of obex.c
Date: Tue, 23 Jul 2024 05:47:07 -0700 (PDT)	[thread overview]
Message-ID: <669fa64b.170a0220.320dfe.312d@mx.google.com> (raw)
In-Reply-To: <20240723110514.8598-1-quic_amisjain@quicinc.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.28 seconds
GitLint                       PASS      0.20 seconds
BuildEll                      PASS      25.67 seconds
BluezMake                     PASS      1798.24 seconds
MakeCheck                     PASS      13.50 seconds
MakeDistcheck                 PASS      185.50 seconds
CheckValgrind                 PASS      265.17 seconds
CheckSmatch                   PASS      374.25 seconds
bluezmakeextell               PASS      127.24 seconds
IncrementalBuild              PASS      1647.88 seconds
ScanBuild                     PASS      1098.73 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2024-07-23 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 11:05 [PATCH BlueZ v5] obex: Move size emit signal to plugins instead of obex.c Amisha Jain
2024-07-23 12:47 ` bluez.test.bot [this message]
2024-07-23 17:12 ` Pauli Virtanen
  -- strict thread matches above, loose matches on Subject: below --
2024-07-03  9:31 Amisha Jain
2024-07-03 11:39 ` [BlueZ,v5] " 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=669fa64b.170a0220.320dfe.312d@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=quic_amisjain@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).