From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, sam@gentoo.org
Subject: RE: shared: define MAX_INPUT for musl
Date: Mon, 30 Jan 2023 23:23:29 -0800 (PST) [thread overview]
Message-ID: <63d8c1f1.050a0220.b063b.8f82@mx.google.com> (raw)
In-Reply-To: <20230131055258.3311810-1-sam@gentoo.org>
[-- 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=717213
---Test result---
Test Summary:
CheckPatch PASS 1.28 seconds
GitLint PASS 0.40 seconds
BuildEll PASS 32.60 seconds
BluezMake PASS 930.49 seconds
MakeCheck PASS 12.57 seconds
MakeDistcheck PASS 172.91 seconds
CheckValgrind PASS 287.70 seconds
CheckSmatch PASS 375.44 seconds
bluezmakeextell PASS 111.96 seconds
IncrementalBuild PASS 749.42 seconds
ScanBuild PASS 1142.01 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-01-31 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 5:52 [PATCH] shared: define MAX_INPUT for musl Sam James
2023-01-31 7:23 ` bluez.test.bot [this message]
2023-01-31 22: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=63d8c1f1.050a0220.b063b.8f82@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sam@gentoo.org \
/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