From: patchwork-bot+bluetooth@kernel.org
To: Emil Velikov via B4 Relay <devnull+emil.l.velikov.gmail.com@kernel.org>
Cc: linux-bluetooth@vger.kernel.org, emil.velikov@collabora.com
Subject: Re: [PATCH BlueZ v4 0/8] Remove support for external plugins
Date: Mon, 29 Jan 2024 19:00:26 +0000 [thread overview]
Message-ID: <170655482624.4760.4346697423571608674.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240129-rm-ext-plugins-v4-0-bfd1e08c7f99@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 29 Jan 2024 14:44:14 +0000 you wrote:
> Hello everyone,
>
> With v4 we have moved from pre-processor to compilation checking for the
> external plugins support.
>
> Namely, as we build without one the dead-code elimination will discard
> all the relevant code. Ultimately this means we compile check both paths
> in order to catch mistakes. Thanks to Luiz for the suggestion.
>
> [...]
Here is the summary with links:
- [BlueZ,v4,1/8] configure, README: introduce --enable-external-plugins
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2a5c9cf632e6
- [BlueZ,v4,2/8] obexd: factor out external plugin support
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=004b5b28a04c
- [BlueZ,v4,3/8] bluetoothd: remove external-dummy plugin
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1db7a00e35c4
- [BlueZ,v4,4/8] bluetoothd: convert external sixaxis plugin to builtin
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9f71892b63f6
- [BlueZ,v4,5/8] bluetoothd: factor out external plugin support
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=109cc8a0f6aa
- [BlueZ,v4,6/8] bluetoothd: don't export internal API
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7a1d3c7c4bc7
- [BlueZ,v4,7/8] bluetoothd: change plugin loading alike obexd
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f174724c76c6
- [BlueZ,v4,8/8] android: export only (android) entrypoint from the modules
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f59f4902bc4e
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-01-29 19:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 14:44 [PATCH BlueZ v4 0/8] Remove support for external plugins Emil Velikov
2024-01-29 14:44 ` Emil Velikov via B4 Relay
2024-01-29 14:44 ` [PATCH BlueZ v4 1/8] configure, README: introduce --enable-external-plugins Emil Velikov
2024-01-29 14:44 ` Emil Velikov via B4 Relay
2024-01-29 17:27 ` Remove support for external plugins bluez.test.bot
2024-01-29 14:44 ` [PATCH BlueZ v4 2/8] obexd: factor out external plugin support Emil Velikov
2024-01-29 14:44 ` Emil Velikov via B4 Relay
2024-01-29 14:44 ` [PATCH BlueZ v4 3/8] bluetoothd: remove external-dummy plugin Emil Velikov
2024-01-29 14:44 ` Emil Velikov via B4 Relay
2024-01-29 14:44 ` [PATCH BlueZ v4 4/8] bluetoothd: convert external sixaxis plugin to builtin Emil Velikov
2024-01-29 14:44 ` Emil Velikov via B4 Relay
2024-01-29 14:44 ` [PATCH BlueZ v4 5/8] bluetoothd: factor out external plugin support Emil Velikov
2024-01-29 14:44 ` Emil Velikov via B4 Relay
2024-01-29 14:44 ` [PATCH BlueZ v4 6/8] bluetoothd: don't export internal API Emil Velikov
2024-01-29 14:44 ` Emil Velikov via B4 Relay
2024-01-29 14:44 ` [PATCH BlueZ v4 7/8] bluetoothd: change plugin loading alike obexd Emil Velikov
2024-01-29 14:44 ` Emil Velikov via B4 Relay
2024-01-29 15:37 ` Paul Menzel
2024-01-29 16:22 ` Luiz Augusto von Dentz
2024-01-29 17:47 ` Emil Velikov
2024-01-29 14:44 ` [PATCH BlueZ v4 8/8] android: export only (android) entrypoint from the modules Emil Velikov
2024-01-29 14:44 ` Emil Velikov via B4 Relay
2024-01-29 15:38 ` Paul Menzel
2024-01-29 19:00 ` 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=170655482624.4760.4346697423571608674.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=devnull+emil.l.velikov.gmail.com@kernel.org \
--cc=emil.velikov@collabora.com \
--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.