mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Zhang <alex@alexyzhang.dev>
To: "José Expósito" <jose.exposito89@gmail.com>, jikos@kernel.org
Cc: benjamin.tissoires@redhat.com, openglfreak@googlemail.com,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] HID: uclogic: Add HID_QUIRK_HIDINPUT_FORCE quirk
Date: Thu, 10 Nov 2022 20:24:36 -0800	[thread overview]
Message-ID: <e1daf0a9-b699-affd-0d14-e46981733096@alexyzhang.dev> (raw)
In-Reply-To: <20221110174056.393697-1-jose.exposito89@gmail.com>

Hi José,

On 11/10/22 9:40 AM, José Expósito wrote:
> Hi everyone,
> 
> About 3 months ago, Torge Matthies sent a patch fixing an issue with
> his XP-Pen Star G640 [1].
> 
> His patch changes the IS_INPUT_APPLICATION() macro to accept
> HID_DG_DIGITIZER. However, it looks like it is not being merged because
> of the possible side effects that changing that macro could generate.
> 
> This patch aims to fix the same issue but using a more conservative
> approach hoping that the bug can be fixed.
> 
> Torge, Alexander, could you test it and confirm that it fixes your
> issues, please?

I tested the patch on commit 4bbf3422df78 and it fixes the issue.

Thank you,
Alexander Zhang

> Thanks a lot in advance,
> José Expósito
> 
> [1] https://lore.kernel.org/linux-input/20220804151832.30373-1-openglfreak@googlemail.com/
> 
> José Expósito (1):
>    HID: uclogic: Add HID_QUIRK_HIDINPUT_FORCE quirk
> 
>   drivers/hid/hid-uclogic-core.c | 1 +
>   1 file changed, 1 insertion(+)
> 

  parent reply	other threads:[~2022-11-11  4:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 17:40 José Expósito
2022-11-10 17:40 ` [PATCH 1/1] " José Expósito
2022-11-11  4:24 ` Alexander Zhang [this message]
2022-11-14 14:10   ` [PATCH 0/1] " Jiri Kosina
2022-11-20  7:01     ` Alexander Zhang
2022-12-06  0:49       ` Alexander Zhang
2022-12-07 11:09         ` José Expósito
2022-12-07 20:43           ` Alexander Zhang

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=e1daf0a9-b699-affd-0d14-e46981733096@alexyzhang.dev \
    --to=alex@alexyzhang.dev \
    --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 \
    --cc=openglfreak@googlemail.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
all inboxes | Powered by JetHome®