linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, mmandlik@google.com
Subject: RE: Emit InterfacesAdded/InterfacesRemoved at correct root path
Date: Tue, 01 Dec 2020 17:48:42 -0800 (PST)	[thread overview]
Message-ID: <5fc6f27a.1c69fb81.49b2d.088f@mx.google.com> (raw)
In-Reply-To: <20201201171838.bluez.v1.1.Idce75740a54d8a860450da8a7a21d55777c87ae9@changeid>

[-- 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=394297

---Test result---

##############################
Test: CheckPatch - PASS

##############################
Test: CheckGitLint - PASS

##############################
Test: CheckBuild - PASS

##############################
Test: MakeCheck - PASS



---
Regards,
Linux Bluetooth


  reply	other threads:[~2020-12-02  1:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02  1:19 [bluez PATCH v1 0/3] Emit InterfacesAdded/InterfacesRemoved at correct root path Manish Mandlik
2020-12-02  1:19 ` [bluez PATCH v1 1/3] adv_monitor: Register client app with app-base-path Manish Mandlik
2020-12-02  1:48   ` bluez.test.bot [this message]
2020-12-02  1:19 ` [bluez PATCH v1 2/3] gdbus: Emit InterfacesAdded/Removed at app root path Manish Mandlik
2020-12-02 17:46   ` Luiz Augusto von Dentz
2020-12-02 18:58     ` Sonny Sasaka
2020-12-02 19:50       ` Luiz Augusto von Dentz
2020-12-02 23:27         ` Sonny Sasaka
2020-12-03  1:10           ` Luiz Augusto von Dentz
2020-12-02  1:19 ` [bluez PATCH v1 3/3] client: Fix add advertisement monitor Manish Mandlik
2020-12-02 17:48   ` 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=5fc6f27a.1c69fb81.49b2d.088f@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mmandlik@google.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).