From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_zijuhu@quicinc.com
Subject: RE: [BlueZ,v2] main: Fix integer configuration option parse failures
Date: Mon, 31 Jul 2023 03:46:17 -0700 (PDT) [thread overview]
Message-ID: <64c790f9.a70a0220.f25d7.cf54@mx.google.com> (raw)
In-Reply-To: <1690795722-29873-1-git-send-email-quic_zijuhu@quicinc.com>
[-- 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=771110
---Test result---
Test Summary:
CheckPatch PASS 0.36 seconds
GitLint PASS 0.26 seconds
BuildEll PASS 32.64 seconds
BluezMake PASS 972.40 seconds
MakeCheck PASS 13.63 seconds
MakeDistcheck PASS 187.41 seconds
CheckValgrind PASS 311.54 seconds
CheckSmatch PASS 411.05 seconds
bluezmakeextell PASS 123.87 seconds
IncrementalBuild PASS 797.78 seconds
ScanBuild PASS 1256.69 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-07-31 10:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 7:46 [PATCH v1] main: Fix a logical error within parse_config_int() Zijun Hu
2023-07-31 8:48 ` Paul Menzel
2023-07-31 8:58 ` quic_zijuhu
2023-07-31 9:16 ` [v1] " bluez.test.bot
2023-07-31 9:28 ` [PATCH BlueZ v2] main: Fix integer configuration option parse failures Zijun Hu
2023-07-31 10:46 ` bluez.test.bot [this message]
2023-07-31 17:50 ` patchwork-bot+bluetooth
2023-07-31 17:50 ` [PATCH v1] main: Fix a logical error within parse_config_int() 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=64c790f9.a70a0220.f25d7.cf54@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=quic_zijuhu@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 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.