public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: Werner Sembach <wse@tuxedocomputers.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Input: atkbd - Correctly map F13 - F24
Date: Tue, 22 Jul 2025 09:04:34 +0200	[thread overview]
Message-ID: <75e0be49-0040-4830-a115-1daea0b73f93@kernel.org> (raw)
In-Reply-To: <e8b1c0b3-83d0-4e0a-9dad-7d59329fe3ce@tuxedocomputers.com>

Hi Werner,

On 21-Jul-25 10:36 PM, Werner Sembach wrote:
> Hi,
> 
> Am 15.05.25 um 14:26 schrieb Werner Sembach:
>> Hi,
>>
>> Am 17.03.25 um 23:23 schrieb Hans de Goede:
>>> Hi Werner,
>>>
>>> On 17-Mar-25 6:00 PM, Werner Sembach wrote:
>>>> [...]
>>> I think this one will apply cleanly without applying patch 1/2
>>> first, so no reason for a resend / v3 AFAICT.
>>>
>>> Let's wait and see what feedback Dmitry have once he can make
>>> some time to take a look at this.
>>
>> Hope a gentle bump is ok by now?
>>
>> Best regards,
>>
>> Werner
> 
> Small bump again, just so that this does not get forgotten.

It might be best to just resend this (rebased on the latest
upstream) as a standalone v3 patch (with my reviewed-by
added).

Regards,

Hans






>>>>>> ---
>>>>>>    drivers/input/keyboard/atkbd.c | 12 ++++++------
>>>>>>    1 file changed, 6 insertions(+), 6 deletions(-)
>>>>>>
>>>>>> diff --git a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
>>>>>> index 3598a21d9d014..4bd6e6ef0715e 100644
>>>>>> --- a/drivers/input/keyboard/atkbd.c
>>>>>> +++ b/drivers/input/keyboard/atkbd.c
>>>>>> @@ -84,12 +84,12 @@ static const unsigned short atkbd_set2_keycode[ATKBD_KEYMAP_SIZE] = {
>>>>>>    #include "hpps2atkbd.h"    /* include the keyboard scancodes */
>>>>>>      #else
>>>>>> -      0, 67, 65, 63, 61, 59, 60, 88,  0, 68, 66, 64, 62, 15, 41,117,
>>>>>> -      0, 56, 42, 93, 29, 16,  2,  0,  0,  0, 44, 31, 30, 17,  3,  0,
>>>>>> -      0, 46, 45, 32, 18,  5,  4, 95,  0, 57, 47, 33, 20, 19,  6,183,
>>>>>> -      0, 49, 48, 35, 34, 21,  7,184,  0,  0, 50, 36, 22, 8,  9,185,
>>>>>> -      0, 51, 37, 23, 24, 11, 10,  0,  0, 52, 53, 38, 39, 25, 12,  0,
>>>>>> -      0, 89, 40,  0, 26, 13,  0,193, 58, 54, 28, 27,  0, 43,  0, 85,
>>>>>> +      0, 67, 65, 63, 61, 59, 60, 88,183, 68, 66, 64, 62, 15, 41,117,
>>>>>> +    184, 56, 42, 93, 29, 16,  2,  0,185,  0, 44, 31, 30, 17,  3,  0,
>>>>>> +    186, 46, 45, 32, 18,  5,  4, 95,187, 57, 47, 33, 20, 19,  6,183,
>>>>>> +    188, 49, 48, 35, 34, 21,  7,184,189,  0, 50, 36, 22, 8,  9,185,
>>>>>> +    190, 51, 37, 23, 24, 11, 10,  0,191, 52, 53, 38, 39, 25, 12,  0,
>>>>>> +    192, 89, 40,  0, 26, 13,  0,193, 58, 54, 28, 27,  0, 43,  0,194,
>>>>>>          0, 86, 91, 90, 92,  0, 14, 94,  0, 79,124, 75, 71,121,  0,  0,
>>>>>>         82, 83, 80, 76, 77, 72,  1, 69, 87, 78, 81, 74, 55, 73, 70, 99,
> 


  reply	other threads:[~2025-07-22  7:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11 18:06 [PATCH v2 1/2] Input: atkbd - Map FN-key for TongFang barebones Werner Sembach
2025-03-11 18:06 ` [PATCH v2 2/2] Input: atkbd - Correctly map F13 - F24 Werner Sembach
2025-03-11 18:10   ` Werner Sembach
2025-03-17 12:06     ` Hans de Goede
2025-03-17 16:47       ` Werner Sembach
2025-03-17 22:22         ` Hans de Goede
2025-03-18 10:20           ` Werner Sembach
2025-03-25 13:18             ` Werner Sembach
2025-03-17 11:58   ` Hans de Goede
2025-03-17 17:00     ` Werner Sembach
2025-03-17 22:23       ` Hans de Goede
2025-03-18 10:21         ` Werner Sembach
2025-05-15 12:26         ` Werner Sembach
2025-07-21 20:36           ` Werner Sembach
2025-07-22  7:04             ` Hans de Goede [this message]
2025-07-22 11:53               ` Werner Sembach
2025-03-11 18:07 ` [PATCH v2 1/2] Input: atkbd - Map FN-key for TongFang barebones Werner Sembach
2025-03-17 11:04 ` Hans de Goede
2025-03-17 15:50   ` Werner Sembach

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=75e0be49-0040-4830-a115-1daea0b73f93@kernel.org \
    --to=hansg@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wse@tuxedocomputers.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