public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Werner Sembach <wse@tuxedocomputers.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Christoffer Sandberg <cs@tuxedo.de>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: i8042 - add TUXEDO InfinityBook Max 16 Gen10 AMD to i8042 quirk table
Date: Wed, 1 Apr 2026 19:19:24 +0200	[thread overview]
Message-ID: <6fd2bbbf-a462-439d-80cd-64d740731b4c@tuxedocomputers.com> (raw)
In-Reply-To: <ac1FzV9dmb_JDXxo@google.com>

Hello Dmitry,

Am 01.04.26 um 18:22 schrieb Dmitry Torokhov:
> Hi Werner,
>
> On Wed, Apr 01, 2026 at 05:48:20PM +0200, Werner Sembach wrote:
>> Hello Dmitry
>>
>> Am 23.02.26 um 22:54 schrieb Dmitry Torokhov:
>>> On Mon, Feb 23, 2026 at 03:20:45PM +0100, Werner Sembach wrote:
>>>> From: Christoffer Sandberg <cs@tuxedo.de>
>>>>
>>>> The device occasionally wakes up from suspend with missing input on the
>>>> internal keyboard and the following suspend attempt results in an instant
>>>> wake-up. The quirks fix both issues for this device.
>>>>
>>>> Signed-off-by: Christoffer Sandberg <cs@tuxedo.de>
>>>> Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
>>> Applied, thank you.
>>>
>> May i ask you where it was applied?
>>
>> I can only find the former patch https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/commit/?id=aed3716db7fff74919cc5775ca3a80c8bb246489
>> for the InfinityBook Max 15 and not this one for the InfinityBook Max 16
>> (both patches have a nearly identical subject line).
> Isn't it this:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/commit/?h=for-linus&id=5839419cffc7788a356428d321e3ec18055c0286
>
> ?
Yes, thanks and sorry I somehow missed to search the for-linus branch.
>
>> Also I forgot to add cc stable, if the patch is not yet applied, can you add
>> it before?
> I added the tags to the commit above (unless it is not the right one,
> they all look very similar).

Yes, it's the one I was talking about. Maybe the next time I add the board name 
to the subject line in the hope that it makes it a little bit more clear.

Thank you very much,

Werner

>
> Thanks.
>

      reply	other threads:[~2026-04-01 17:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 14:20 [PATCH] Input: i8042 - add TUXEDO InfinityBook Max 16 Gen10 AMD to i8042 quirk table Werner Sembach
2026-02-23 21:54 ` Dmitry Torokhov
2026-04-01 15:48   ` Werner Sembach
2026-04-01 16:22     ` Dmitry Torokhov
2026-04-01 17:19       ` Werner Sembach [this message]

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=6fd2bbbf-a462-439d-80cd-64d740731b4c@tuxedocomputers.com \
    --to=wse@tuxedocomputers.com \
    --cc=cs@tuxedo.de \
    --cc=dmitry.torokhov@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