From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1 1/3] gdbus: Add testing flags
Date: Wed, 24 Apr 2024 19:10:30 +0000 [thread overview]
Message-ID: <171398583005.8080.17570797656586220655.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240423224603.2124790-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 23 Apr 2024 18:46:01 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This adds testing flags which are similar to experimental but are only
> available for testing.
> ---
> gdbus/gdbus.h | 23 +++++++++++++++++++++++
> gdbus/object.c | 36 ++++++++++++++++++++++++++++++++++++
> 2 files changed, 59 insertions(+)
Here is the summary with links:
- [BlueZ,v1,1/3] gdbus: Add testing flags
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d8f3a3fa497f
- [BlueZ,v1,2/3] main.conf: Add support for testing interfaces
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e7578f9ddd07
- [BlueZ,v1,3/3] ccp: Mark plugin for testing
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=02ade13c439f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-04-24 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 22:46 [PATCH BlueZ v1 1/3] gdbus: Add testing flags Luiz Augusto von Dentz
2024-04-23 22:46 ` [PATCH BlueZ v1 2/3] main.conf: Add support for testing interfaces Luiz Augusto von Dentz
2024-04-23 22:46 ` [PATCH BlueZ v1 3/3] ccp: Mark plugin for testing Luiz Augusto von Dentz
2024-04-24 19:10 ` patchwork-bot+bluetooth [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=171398583005.8080.17570797656586220655.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--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).