From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/6] shared/csip: Fix returning invalid data to attribute Size reads
Date: Mon, 02 Oct 2023 18:50:54 -0700 (PDT) [thread overview]
Message-ID: <651b737e.020a0220.baf30.00ef@mx.google.com> (raw)
In-Reply-To: <20231002231311.3104749-1-luiz.dentz@gmail.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=789421
---Test result---
Test Summary:
CheckPatch PASS 2.70 seconds
GitLint PASS 7.02 seconds
BuildEll PASS 28.76 seconds
BluezMake PASS 979.14 seconds
MakeCheck PASS 12.63 seconds
MakeDistcheck PASS 163.32 seconds
CheckValgrind PASS 264.15 seconds
CheckSmatch PASS 356.79 seconds
bluezmakeextell PASS 109.03 seconds
IncrementalBuild PASS 4989.81 seconds
ScanBuild PASS 1092.62 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-10-03 1:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 23:13 [PATCH BlueZ 1/6] shared/csip: Fix returning invalid data to attribute Size reads Luiz Augusto von Dentz
2023-10-02 23:13 ` [PATCH BlueZ 2/6] shared/csip: Fix not requiring encryption Luiz Augusto von Dentz
2023-10-02 23:13 ` [PATCH BlueZ 3/6] shared/csip: Fix not always reading SIRK value Luiz Augusto von Dentz
2023-10-02 23:13 ` [PATCH BlueZ 4/6] device: Add btd_device_get_ltk Luiz Augusto von Dentz
2023-10-02 23:13 ` [PATCH BlueZ 5/6] csip: Add support for SIRK encryption Luiz Augusto von Dentz
2023-10-02 23:13 ` [PATCH BlueZ 6/6] main.conf: Fix default of CSIS.encrypt Luiz Augusto von Dentz
2023-10-03 1:50 ` bluez.test.bot [this message]
2023-10-03 23:20 ` [PATCH BlueZ 1/6] shared/csip: Fix returning invalid data to attribute Size reads 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=651b737e.020a0220.baf30.00ef@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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).