From: patchwork-bot+bluetooth@kernel.org
To: Thomas Perale <thomas.perale@mind.be>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 0/2] fix build error with --enable-hid and --enable-hog options
Date: Thu, 01 May 2025 19:10:31 +0000 [thread overview]
Message-ID: <174612663154.3052720.4219537316370232114.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250501163536.1283827-1-thomas.perale@mind.be>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 1 May 2025 18:35:34 +0200 you wrote:
> This patch series fixes build failures when --enable-hid and --enable-hog
> are not enabled together. The issue is documented in the following ticket:
>
> https://github.com/bluez/bluez/issues/1228.
>
> Compiling with the --enable-hid --disable-hog option would give an
> error because the HID plugin relied on functions defined in the HoG
> plugin:
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/2] input: fix HID compilation w/o HoG
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b111b5e15eb7
- [BlueZ,v2,2/2] input: fix HoG compilation w/o HID
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9c52188d7530
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:[~2025-05-01 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 16:35 [PATCH BlueZ v2 0/2] fix build error with --enable-hid and --enable-hog options Thomas Perale
2025-05-01 16:35 ` [PATCH BlueZ v2 1/2] input: fix HID compilation w/o HoG Thomas Perale
2025-05-01 17:56 ` fix build error with --enable-hid and --enable-hog options bluez.test.bot
2025-05-01 16:35 ` [PATCH BlueZ v2 2/2] input: fix HoG compilation w/o HID Thomas Perale
2025-05-01 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=174612663154.3052720.4219537316370232114.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=thomas.perale@mind.be \
/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.