linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, wangyouwan@uniontech.com
Subject: RE: obexd: Fix the code style
Date: Tue, 05 Jul 2022 03:32:34 -0700 (PDT)	[thread overview]
Message-ID: <62c41342.1c69fb81.8d3fe.2314@mx.google.com> (raw)
In-Reply-To: <20220705092952.11868-1-wangyouwan@uniontech.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.86 seconds
GitLint                       PASS      0.58 seconds
Prep - Setup ELL              PASS      26.18 seconds
Build - Prep                  PASS      0.61 seconds
Build - Configure             PASS      8.38 seconds
Build - Make                  PASS      995.88 seconds
Make Check                    PASS      12.16 seconds
Make Check w/Valgrind         PASS      292.34 seconds
Make Distcheck                PASS      244.11 seconds
Build w/ext ELL - Configure   PASS      8.88 seconds
Build w/ext ELL - Make        PASS      84.09 seconds
Incremental Build w/ patches  PASS      0.00 seconds
Scan Build                    PASS      513.76 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-07-05 10:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05  9:29 [PATCH] obexd: Fix the code style Youwan Wang
2022-07-05 10:32 ` bluez.test.bot [this message]
2022-07-05 17:20 ` patchwork-bot+bluetooth

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=62c41342.1c69fb81.8d3fe.2314@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 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).