From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, daniel@simko.xyz
Subject: RE: [BlueZ] profiles: Fix segfault when using headset controls
Date: Sat, 10 Oct 2020 16:33:02 -0700 (PDT) [thread overview]
Message-ID: <5f8244ae.1c69fb81.ce543.bf05@mx.google.com> (raw)
In-Reply-To: <20201010222719.439956-1-daniel@simko.xyz>
[-- Attachment #1: Type: text/plain, Size: 557 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=362639
---Test result---
##############################
Test: CheckPatch - PASS
##############################
Test: CheckGitLint - PASS
##############################
Test: CheckBuild - PASS
##############################
Test: MakeCheck - PASS
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2020-10-10 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 22:27 [PATCH BlueZ] profiles: Fix segfault when using headset controls Daniel Šimko
2020-10-10 23:33 ` bluez.test.bot [this message]
2020-10-12 17:26 ` [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=5f8244ae.1c69fb81.ce543.bf05@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=daniel@simko.xyz \
--cc=linux-bluetooth@vger.kernel.org \
/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).