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 1/2] main.conf: Split Kernel Experimental UUIDs from Experimental
Date: Thu, 16 Jun 2022 19:40:13 +0000 [thread overview]
Message-ID: <165540841319.1034.7520891078846747091.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220614215609.596687-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, 14 Jun 2022 14:56:08 -0700 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This splits kernel experimental UUIDs from D-Bus Experimental interface
> so they can be controlled indenpendetly.
> ---
> src/adapter.c | 28 ++++++++++++++++---------
> src/btd.h | 5 +++--
> src/main.c | 57 ++++++++++++++++++++++++++++++---------------------
> src/main.conf | 8 ++++++--
> 4 files changed, 61 insertions(+), 37 deletions(-)
Here is the summary with links:
- [BlueZ,1/2] main.conf: Split Kernel Experimental UUIDs from Experimental
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a5382ba2f09c
- [BlueZ,2/2] bluetoothd.rst: Document -K/--kernel option
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=afc8c8f56fa2
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:[~2022-06-16 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 21:56 [PATCH BlueZ 1/2] main.conf: Split Kernel Experimental UUIDs from Experimental Luiz Augusto von Dentz
2022-06-14 21:56 ` [PATCH BlueZ 2/2] bluetoothd.rst: Document -K/--kernel option Luiz Augusto von Dentz
2022-06-14 23:57 ` [BlueZ,1/2] main.conf: Split Kernel Experimental UUIDs from Experimental bluez.test.bot
2022-06-16 19:40 ` 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=165540841319.1034.7520891078846747091.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).