From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ] media: Fix memory leak
Date: Tue, 09 Nov 2021 14:37:38 -0800 (PST) [thread overview]
Message-ID: <618af832.1c69fb81.e5dd0.6ba1@mx.google.com> (raw)
In-Reply-To: <20211109215322.1124566-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 884 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=577661
---Test result---
Test Summary:
CheckPatch PASS 1.30 seconds
GitLint PASS 0.87 seconds
Prep - Setup ELL PASS 49.54 seconds
Build - Prep PASS 0.46 seconds
Build - Configure PASS 9.05 seconds
Build - Make PASS 204.90 seconds
Make Check PASS 9.80 seconds
Make Distcheck PASS 244.96 seconds
Build w/ext ELL - Configure PASS 9.09 seconds
Build w/ext ELL - Make PASS 194.61 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2021-11-09 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 21:53 [PATCH BlueZ] media: Fix memory leak Luiz Augusto von Dentz
2021-11-09 22:37 ` bluez.test.bot [this message]
2021-11-09 22:46 ` [BlueZ] " 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=618af832.1c69fb81.e5dd0.6ba1@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