Linux Input/HID development
 help / color / mirror / Atom feed
From: "José Expósito" <jose.exposito89@gmail.com>
To: Alexander Zhang <alex@alexyzhang.dev>
Cc: Jiri Kosina <jikos@kernel.org>,
	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: Wed, 7 Dec 2022 12:09:55 +0100	[thread overview]
Message-ID: <Y5B0gwGZJ/PQyV4+@fedora> (raw)
In-Reply-To: <1dc9d0ba-4836-dfc6-8bf2-322ce3b5c24d@alexyzhang.dev>

Hi Alexander,

On Mon, Dec 05, 2022 at 04:49:10PM -0800, Alexander Zhang wrote:
> Hello,
> 
> On 11/19/22 11:01 PM, Alexander Zhang wrote:
> > On 11/14/22 6:10 AM, Jiri Kosina wrote:
> > > On Thu, 10 Nov 2022, Alexander Zhang wrote:
> > > 
> > > > 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.
> > > 
> > > I will add
> > > 
> > >     Tested-by: Alexander Zhang <alex@alexyzhang.dev>
> > > 
> > > to the commit; please speak up if you disagree.
> > 
> > I'm not sure if you're still waiting for a response from me but I'm fine
> > with that.
> 
> Is there something preventing this patch from being merged? I'm not very
> familiar with the kernel development process.

The patch is already applied in the for-next branch, you can find it here:
https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git/commit/?h=for-next&id=3405a4beaaa8

Jose

> Best,
> Alexander Zhang

  reply	other threads:[~2022-12-07 11:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 17:40 [PATCH 0/1] HID: uclogic: Add HID_QUIRK_HIDINPUT_FORCE quirk José Expósito
2022-11-10 17:40 ` [PATCH 1/1] " José Expósito
2022-11-11  4:24 ` [PATCH 0/1] " Alexander Zhang
2022-11-14 14:10   ` Jiri Kosina
2022-11-20  7:01     ` Alexander Zhang
2022-12-06  0:49       ` Alexander Zhang
2022-12-07 11:09         ` José Expósito [this message]
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=Y5B0gwGZJ/PQyV4+@fedora \
    --to=jose.exposito89@gmail.com \
    --cc=alex@alexyzhang.dev \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --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