From: Nikolai Kondrashov <spbnick@gmail.com>
To: "José Expósito" <jose.exposito89@gmail.com>
Cc: jikos@kernel.org, benjamin.tissoires@redhat.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] UCLogic: Filtering unsupported HUION tablets
Date: Wed, 20 Jul 2022 21:13:39 +0300 [thread overview]
Message-ID: <3cdbcfe5-bb7e-2677-730f-f250e2d33f0c@gmail.com> (raw)
In-Reply-To: <20220720175444.GA10744@elementary>
On 7/20/22 20:54, José Expósito wrote:
> Hi!
>
> On Wed, Jul 20, 2022 at 08:45:55PM +0300, Nikolai Kondrashov wrote:
>> On 7/20/22 20:36, José Expósito wrote:
>>> I don't know about any broken device handled by the driver, so there is
>>> no need to add new code yet :)
>>> I'll try to keep an eye on DIGImend's issue tracker now that the code
>>> present in the upstream kernel is being released by many distros.
>>
>> If you have the time, backporting your changes to digimend-kernel-drivers
>> would get you feedback much faster :)
>>
>> I can do a release once we get the code in.
>
> I already opened a PR a few months ago:
> https://github.com/DIGImend/digimend-kernel-drivers/pull/598
>
> But more code has been merged since then. I'll try to backport the
> latest changes this weekend and ping you on GitHub once it is
> ready for review again.
Ah, sorry, I rarely look at DIGImend notifications 🙈
Could you send me an email once you got something ready for review?
Thank you!
Nick
next prev parent reply other threads:[~2022-07-20 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 17:29 [RFC] UCLogic: Filtering unsupported HUION tablets José Expósito
2022-07-19 9:57 ` Nikolai Kondrashov
2022-07-20 17:36 ` José Expósito
2022-07-20 17:45 ` Nikolai Kondrashov
2022-07-20 17:54 ` José Expósito
2022-07-20 18:13 ` Nikolai Kondrashov [this message]
2022-07-24 11:05 ` José Expósito
2022-08-08 7:44 ` Nikolai Kondrashov
2022-08-08 16:15 ` José Expósito
2022-07-21 9:39 ` Bastien Nocera
2022-07-24 11:14 ` José Expósito
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=3cdbcfe5-bb7e-2677-730f-f250e2d33f0c@gmail.com \
--to=spbnick@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=jose.exposito89@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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 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).