All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, wangyouwan@uniontech.com
Subject: RE: obexd: fix crashed after cancel the on-going transfer
Date: Tue, 28 Jun 2022 23:36:23 -0700 (PDT)	[thread overview]
Message-ID: <62bbf2e7.1c69fb81.e8839.0bb1@mx.google.com> (raw)
In-Reply-To: <20220629051902.23452-1-wangyouwan@uniontech.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.50 seconds
GitLint                       PASS      1.04 seconds
Prep - Setup ELL              PASS      44.29 seconds
Build - Prep                  PASS      0.68 seconds
Build - Configure             PASS      8.67 seconds
Build - Make                  PASS      1455.08 seconds
Make Check                    PASS      12.42 seconds
Make Check w/Valgrind         PASS      448.35 seconds
Make Distcheck                PASS      243.59 seconds
Build w/ext ELL - Configure   PASS      8.71 seconds
Build w/ext ELL - Make        PASS      1467.38 seconds
Incremental Build with patchesPASS      0.00 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-06-29  6:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29  5:19 [PATCH] obexd: fix crashed after cancel the on-going transfer Youwan Wang
2022-06-29  6:36 ` bluez.test.bot [this message]
2022-07-01  5:52 Youwan Wang
2022-07-01  6:53 ` bluez.test.bot
2022-07-01  8:06 [PATCH] " Youwan Wang
2022-07-01  9:17 ` bluez.test.bot
2022-07-01  9:41 [PATCH] " Youwan Wang
2022-07-01 10:25 ` bluez.test.bot
2022-07-04  3:23 [PATCH] " Youwan Wang
2022-07-04  4:34 ` bluez.test.bot
2022-07-08  6:25 [PATCH] " Youwan Wang
2022-07-08  7:06 ` 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=62bbf2e7.1c69fb81.e8839.0bb1@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=wangyouwan@uniontech.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.