From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v2] Bluetooth: hci_sync: fix memory leak in hci_update_adv_data()
Date: Mon, 09 Jan 2023 13:47:46 -0800 (PST) [thread overview]
Message-ID: <63bc8b82.370a0220.f84ff.2eb7@mx.google.com> (raw)
In-Reply-To: <20230109212237.3209300-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1420 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=710258
---Test result---
Test Summary:
CheckPatch PASS 0.67 seconds
GitLint PASS 0.33 seconds
SubjectPrefix PASS 0.12 seconds
BuildKernel PASS 31.67 seconds
CheckAllWarning PASS 35.17 seconds
CheckSparse PASS 39.31 seconds
CheckSmatch PASS 108.95 seconds
BuildKernel32 PASS 30.51 seconds
TestRunnerSetup PASS 441.76 seconds
TestRunner_l2cap-tester PASS 16.00 seconds
TestRunner_iso-tester PASS 16.45 seconds
TestRunner_bnep-tester PASS 5.54 seconds
TestRunner_mgmt-tester PASS 107.57 seconds
TestRunner_rfcomm-tester PASS 8.77 seconds
TestRunner_sco-tester PASS 8.04 seconds
TestRunner_ioctl-tester PASS 9.25 seconds
TestRunner_mesh-tester PASS 6.85 seconds
TestRunner_smp-tester PASS 7.98 seconds
TestRunner_userchan-tester PASS 5.75 seconds
IncrementalBuild PASS 28.72 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-01-09 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 21:22 [PATCH v2] Bluetooth: hci_sync: fix memory leak in hci_update_adv_data() Luiz Augusto von Dentz
2023-01-09 21:47 ` bluez.test.bot [this message]
2023-01-09 23:40 ` patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2023-01-10 6:44 Zhengchao Shao
2023-01-10 6:42 ` [v2] " bluez.test.bot
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=63bc8b82.370a0220.f84ff.2eb7@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).