From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ 1/2] profiles/audio: Quiet plug-in warnings
Date: Mon, 02 Dec 2024 21:40:33 +0000 [thread overview]
Message-ID: <173317563374.3902418.18033009959697183180.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241127115007.1303616-1-hadess@hadess.net>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 27 Nov 2024 12:49:52 +0100 you wrote:
> A normal daemon start should not throw warnings on a system in the
> default configuration. Quiet the plug-in warnings that require
> experimental features to be enabled. They will still appear in the debug
> output.
>
> bluetoothd[896]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
>
> [...]
Here is the summary with links:
- [BlueZ,1/2] profiles/audio: Quiet plug-in warnings
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fdcde2ce2112
- [BlueZ,2/2] plugin: Quiet start-up warnings
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=252883241228
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-12-02 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 11:49 [BlueZ 1/2] profiles/audio: Quiet plug-in warnings Bastien Nocera
2024-11-27 11:49 ` [BlueZ 2/2] plugin: Quiet start-up warnings Bastien Nocera
2024-11-27 13:27 ` [BlueZ,1/2] profiles/audio: Quiet plug-in warnings bluez.test.bot
2024-12-02 21: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=173317563374.3902418.18033009959697183180.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=hadess@hadess.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.