From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: Bluetooth: L2CAP: Fix attempting to access uninitialized memory
Date: Mon, 31 Oct 2022 17:18:18 -0700 (PDT) [thread overview]
Message-ID: <636065ca.050a0220.d770d.cefd@mx.google.com> (raw)
In-Reply-To: <20221031231052.2718430-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1261 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=690675
---Test result---
Test Summary:
CheckPatch PASS 1.42 seconds
GitLint PASS 0.83 seconds
SubjectPrefix PASS 0.64 seconds
BuildKernel PASS 45.44 seconds
BuildKernel32 PASS 40.67 seconds
Incremental Build with patchesPASS 63.07 seconds
TestRunner: Setup PASS 702.91 seconds
TestRunner: l2cap-tester PASS 21.89 seconds
TestRunner: iso-tester PASS 22.33 seconds
TestRunner: bnep-tester PASS 8.51 seconds
TestRunner: mgmt-tester PASS 136.60 seconds
TestRunner: rfcomm-tester PASS 13.46 seconds
TestRunner: sco-tester PASS 12.76 seconds
TestRunner: ioctl-tester PASS 14.63 seconds
TestRunner: mesh-tester PASS 9.94 seconds
TestRunner: smp-tester PASS 12.11 seconds
TestRunner: userchan-tester PASS 8.51 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-11-01 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 23:10 [PATCH] Bluetooth: L2CAP: Fix attempting to access uninitialized memory Luiz Augusto von Dentz
2022-11-01 0:18 ` bluez.test.bot [this message]
2022-11-01 18:56 ` An, Tedd
2022-11-01 20:50 ` 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=636065ca.050a0220.d770d.cefd@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 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.