From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, mmandlik@google.com
Subject: RE: [BlueZ,v5,1/2] vhci: Add support to trigger devcoredump and read the dump file
Date: Thu, 30 Mar 2023 00:28:43 -0700 (PDT) [thread overview]
Message-ID: <64253a2b.370a0220.d821d.8260@mx.google.com> (raw)
In-Reply-To: <20230329230734.BlueZ.v5.1.I21ac5a143b0e42eef4ff71ef04ef0e53a294932a@changeid>
[-- Attachment #1: Type: text/plain, Size: 947 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=735224
---Test result---
Test Summary:
CheckPatch PASS 1.21 seconds
GitLint PASS 0.70 seconds
BuildEll PASS 27.03 seconds
BluezMake PASS 875.35 seconds
MakeCheck PASS 11.64 seconds
MakeDistcheck PASS 150.61 seconds
CheckValgrind PASS 247.98 seconds
CheckSmatch PASS 333.21 seconds
bluezmakeextell PASS 98.98 seconds
IncrementalBuild PASS 1423.83 seconds
ScanBuild PASS 1017.98 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-03-30 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 6:08 [BlueZ PATCH v5 1/2] vhci: Add support to trigger devcoredump and read the dump file Manish Mandlik
2023-03-30 6:08 ` [BlueZ PATCH v5 2/2] mgmt-tester: Add devcoredump tests Manish Mandlik
2023-03-30 7:28 ` bluez.test.bot [this message]
2023-03-30 18:10 ` [BlueZ PATCH v5 1/2] vhci: Add support to trigger devcoredump and read the dump file patchwork-bot+bluetooth
2023-03-30 18:18 ` Luiz Augusto von Dentz
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=64253a2b.370a0220.d821d.8260@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mmandlik@google.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