From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: Bluetooth: L2CAP: Fix build errors in some archs
Date: Fri, 12 Aug 2022 16:05:53 -0700 (PDT) [thread overview]
Message-ID: <62f6dcd1.050a0220.5ebd8.1241@mx.google.com> (raw)
In-Reply-To: <20220812223939.530428-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1100 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=667285
---Test result---
Test Summary:
CheckPatch PASS 1.34 seconds
GitLint PASS 0.79 seconds
SubjectPrefix PASS 0.58 seconds
BuildKernel PASS 39.92 seconds
BuildKernel32 PASS 35.20 seconds
Incremental Build with patchesPASS 49.68 seconds
TestRunner: Setup PASS 584.32 seconds
TestRunner: l2cap-tester PASS 19.76 seconds
TestRunner: bnep-tester PASS 7.80 seconds
TestRunner: mgmt-tester PASS 118.02 seconds
TestRunner: rfcomm-tester PASS 11.69 seconds
TestRunner: sco-tester PASS 11.30 seconds
TestRunner: smp-tester PASS 11.48 seconds
TestRunner: userchan-tester PASS 8.07 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-08-12 23:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 22:39 [PATCH] Bluetooth: L2CAP: Fix build errors in some archs Luiz Augusto von Dentz
2022-08-12 23:05 ` bluez.test.bot [this message]
2022-08-12 23:12 ` Luiz Augusto von Dentz
2022-08-13 7:30 ` Sudip Mukherjee
2022-08-13 19:32 ` Luiz Augusto von Dentz
2022-08-14 10:48 ` Sudip Mukherjee
2022-08-15 17:55 ` Luiz Augusto von Dentz
2022-08-18 21:28 ` Sudip Mukherjee
2022-08-18 22:03 ` Luiz Augusto von Dentz
2022-08-19 7:28 ` Sudip Mukherjee
2022-08-19 18:49 ` 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=62f6dcd1.050a0220.5ebd8.1241@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