All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, purendra.singh@nxp.com
Subject: RE: Changed Obex default timeout
Date: Thu, 19 Oct 2023 01:44:09 -0700 (PDT)	[thread overview]
Message-ID: <6530ec59.0c0a0220.313ab.3024@mx.google.com> (raw)
In-Reply-To: <20231019071651.4773-2-purendra.singh@nxp.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=794595

---Test result---

Test Summary:
CheckPatch                    PASS      0.50 seconds
GitLint                       PASS      0.34 seconds
BuildEll                      PASS      29.22 seconds
BluezMake                     PASS      1046.14 seconds
MakeCheck                     PASS      12.19 seconds
MakeDistcheck                 PASS      178.48 seconds
CheckValgrind                 PASS      277.44 seconds
CheckSmatch                   PASS      367.49 seconds
bluezmakeextell               PASS      119.40 seconds
IncrementalBuild              PASS      854.28 seconds
ScanBuild                     PASS      1126.69 seconds



---
Regards,
Linux Bluetooth


      parent reply	other threads:[~2023-10-19  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  7:16 [PATCH BlueZ v1 0/1] Changed Obex default timeout Purendra-Singh
2023-10-19  7:16 ` [PATCH BlueZ v1 1/1] gobex/gobex.c : Changed default obex timeout Purendra-Singh
2023-10-19  8:06   ` Paul Menzel
2023-10-19  8:44   ` bluez.test.bot [this message]

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=6530ec59.0c0a0220.313ab.3024@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=purendra.singh@nxp.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 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.