From: patchwork-bot+bluetooth@kernel.org
To: Marek Czerski <ma.czerski@gmail.com>
Cc: hadess@hadess.net, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2] sixaxis: Fix pairing Esperanza EGG109k controller
Date: Fri, 24 Apr 2026 14:30:05 +0000 [thread overview]
Message-ID: <177704100580.1564116.17907227393597169449.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260422212045.1325603-1-ma.czerski@gmail.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 22 Apr 2026 23:20:45 +0200 you wrote:
> This change is required for Esperanza EGG109k ps controller clone.
> EGG109k looks like PS3 controller but presents itself to the system
> as PS4 controller. It does not respond to 0x81 command.
> Command 0x12 contains both the device bluetooth address as well as
> configured host bluetooth address, so it can be used to query
> both. Kernel driver hid-playstation also uses 0x12 command for that.
>
> [...]
Here is the summary with links:
- [BlueZ,v2] sixaxis: Fix pairing Esperanza EGG109k controller
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=49e2a15adc79
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:[~2026-04-24 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 12:30 [PATCH BlueZ] sixaxis: DS4: use 0x12 cmd to get device bdaddr Marek Czerski
2026-04-04 13:25 ` [BlueZ] " bluez.test.bot
2026-04-16 9:57 ` [PATCH BlueZ] " Bastien Nocera
2026-04-22 21:20 ` [PATCH BlueZ v2] sixaxis: Fix pairing Esperanza EGG109k controller Marek Czerski
2026-04-22 22:20 ` [BlueZ,v2] " bluez.test.bot
2026-04-23 7:05 ` Marek Czerski
2026-04-23 12:43 ` [PATCH BlueZ v2] " Bastien Nocera
2026-04-24 14:30 ` 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=177704100580.1564116.17907227393597169449.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ma.czerski@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