linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/2] shared/bap: Fix not detaching streams when PAC is removed
Date: Mon, 23 Jan 2023 14:55:09 -0800 (PST)	[thread overview]
Message-ID: <63cf104d.e90a0220.b219e.1269@mx.google.com> (raw)
In-Reply-To: <20230123213212.3187747-1-luiz.dentz@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 948 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=714905

---Test result---

Test Summary:
CheckPatch                    PASS      1.04 seconds
GitLint                       PASS      0.69 seconds
BuildEll                      PASS      30.05 seconds
BluezMake                     PASS      950.84 seconds
MakeCheck                     PASS      12.74 seconds
MakeDistcheck                 PASS      165.14 seconds
CheckValgrind                 PASS      272.77 seconds
CheckSmatch                   PASS      367.49 seconds
bluezmakeextell               PASS      112.71 seconds
IncrementalBuild              PASS      1569.53 seconds
ScanBuild                     PASS      1132.55 seconds



---
Regards,
Linux Bluetooth


      parent reply	other threads:[~2023-01-23 22:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 21:32 [PATCH BlueZ 1/2] shared/bap: Fix not detaching streams when PAC is removed Luiz Augusto von Dentz
2023-01-23 21:32 ` [PATCH BlueZ 2/2] bap: Fix not setting stream to NULL Luiz Augusto von Dentz
2023-01-23 22:55 ` bluez.test.bot [this message]

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=63cf104d.e90a0220.b219e.1269@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).