From: Denis Benato <denis.benato@linux.dev>
To: Mirian Shilakadze <mirian@msh.ge>, 'Jiri Kosina' <jikos@kernel.org>
Cc: 'Benjamin Tissoires' <bentiss@kernel.org>,
'Dmitry Torokhov' <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"Derek J. Clark" <derekjohn.clark@gmail.com>
Subject: Re: [PATCH v5 0/2] HID: flydigi: add support for vader 5 pro
Date: Fri, 6 Nov 2026 17:46:03 +0100 [thread overview]
Message-ID: <1a79cc1d-1c47-4a87-82bd-304c63deabd7@linux.dev> (raw)
In-Reply-To: <9231fd80-a35e-45e6-a608-858e60a7faee@msh.ge>
On 11/6/26 17:02, Mirian Shilakadze wrote:
> On 11/6/26 4:03 AM, Denis Benato wrote:
>>> Should the driver check the flag and warn or turn it on itself with 0x11?
>> I think it should have a sysfs property allowing to change it and also set
>> the most reasonable value at probe.
>
> Makes sense to me.
>
>> Since you two have the whole range of hardware and SDL has working
>> code why don't you take over? It would surely be better than me making
>> the bridge since you do own hardware and care about it.
>>
>> Let me know if you are interested and I will be more than happy to
>> make that happen!
> Yes, I'm interested. Thanks for the offer!
>
> Could you Cc your friend so we can coordinate? It would also help to
> know what the recent firmware update changed.
I have requested him to contact you via email.
He uses discord: you may opt to use OGC server (ex asus-linux) or
communicate between you two.
> If it works for both of you, I'm happy to send the next versions of the
> series and handle the review.
Sure, I also have another driver version to be cleaned up with apex 6
support.
> How would you like the handover to work? If I take it over, I would keep
> your authorship on the existing code with Co-developed-by and
> Signed-off-by. It would be great if you could stay in Cc and review.
As per rules you will need to keep my signed-off-by and git send email
will automatically include me due to that.
I don't promise timely reviews as I have quite a few things to take care of
(asus, mostly) but I will surely try.
> Thanks,
> Mirian Shilakadze
>
>
next prev parent reply other threads:[~2026-11-06 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 23:51 [PATCH v5 0/2] HID: flydigi: add support for vader 5 pro MIrian Shilakadze
2026-11-06 0:03 ` Denis Benato
2026-11-06 16:02 ` Mirian Shilakadze
2026-11-06 16:46 ` Denis Benato [this message]
2026-11-06 17:19 ` Mirian Shilakadze
-- strict thread matches above, loose matches on Subject: below --
2026-09-15 17:14 Denis Benato
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=1a79cc1d-1c47-4a87-82bd-304c63deabd7@linux.dev \
--to=denis.benato@linux.dev \
--cc=bentiss@kernel.org \
--cc=derekjohn.clark@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mirian@msh.ge \
/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.