From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, soenke.huster@eknoes.de
Subject: RE: [v2,RESEND] Bluetooth: virtio_bt: Use skb_put to set length
Date: Wed, 12 Oct 2022 01:21:54 -0700 (PDT) [thread overview]
Message-ID: <63467922.170a0220.4746f.1820@mx.google.com> (raw)
In-Reply-To: <20221012074507.8157-1-soenke.huster@eknoes.de>
[-- Attachment #1: Type: text/plain, Size: 1262 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=684698
---Test result---
Test Summary:
CheckPatch PASS 0.97 seconds
GitLint PASS 0.50 seconds
SubjectPrefix PASS 0.31 seconds
BuildKernel PASS 47.90 seconds
BuildKernel32 PASS 42.79 seconds
Incremental Build with patchesPASS 62.39 seconds
TestRunner: Setup PASS 702.33 seconds
TestRunner: l2cap-tester PASS 21.62 seconds
TestRunner: iso-tester PASS 22.65 seconds
TestRunner: bnep-tester PASS 8.55 seconds
TestRunner: mgmt-tester PASS 137.07 seconds
TestRunner: rfcomm-tester PASS 13.42 seconds
TestRunner: sco-tester PASS 12.48 seconds
TestRunner: ioctl-tester PASS 14.80 seconds
TestRunner: mesh-tester PASS 10.57 seconds
TestRunner: smp-tester PASS 12.28 seconds
TestRunner: userchan-tester PASS 8.83 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-10-12 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 7:05 [PATCH v2] Bluetooth: virtio_bt: Use skb_put to set length Soenke Huster
2022-07-27 8:05 ` [v2] " bluez.test.bot
2022-10-12 7:45 ` [PATCH v2 RESEND] " Soenke Huster
2022-10-12 8:21 ` bluez.test.bot [this message]
2022-10-12 20:00 ` 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=63467922.170a0220.4746f.1820@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=soenke.huster@eknoes.de \
/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