From: Rahul Rameshbabu <sergeantsagara@protonmail.com>
To: Alexander Koskovich <AKoskovich@pm.me>
Cc: roderick.colenbrander@sony.com, jikos@kernel.org,
benjamin.tissoires@redhat.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] hid-playstation: Fix button maps for the DualSense Edge controller
Date: Tue, 28 Nov 2023 02:16:27 +0000 [thread overview]
Message-ID: <87bkbeei6g.fsf@protonmail.com> (raw)
In-Reply-To: <20231126001544.747151-1-akoskovich@pm.me>
On Sun, 26 Nov, 2023 00:15:49 +0000 "Alexander Koskovich" <AKoskovich@pm.me> wrote:
> This brings functionality of the DualSense Edge controller inline
> with the stock PS5 controller.
>
> Signed-off-by: Alexander Koskovich <akoskovich@pm.me>
> ---
Will provide a follow-up to the relevant discussion.
https://lore.kernel.org/linux-input/P8jVfYBAwiM_8MIgshN0osVVfshfBH2-oZCQuqoqh0Hy76_031zuZvYXWl0edtfTUwDOSNlc5priSRXI3G5dboVh5VPbcdxzAcEF7EvUVgo=@protonmail.com/T/#t
Since I assume this patch was not actually tested to resolve the issue
based on the evtest results, I think we should drop this patch. Will
mention some details I might have with regards to the behavior you are
seeing with Steam/Proton specifically.
--
Thanks,
Rahul Rameshbabu
next prev parent reply other threads:[~2023-11-28 2:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 0:15 [PATCH 1/1] hid-playstation: Fix button maps for the DualSense Edge controller Alexander Koskovich
2023-11-28 2:16 ` Rahul Rameshbabu [this message]
2023-11-28 2:19 ` Alexander Koskovich
2023-11-28 2:36 ` Roderick Colenbrander
-- strict thread matches above, loose matches on Subject: below --
2023-11-28 2:34 Rahul Rameshbabu
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=87bkbeei6g.fsf@protonmail.com \
--to=sergeantsagara@protonmail.com \
--cc=AKoskovich@pm.me \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roderick.colenbrander@sony.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).