From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Gergo Koteles <soyer@irl.hu>
Cc: Ike Panhc <ike.pan@canonical.com>,
Hans de Goede <hdegoede@redhat.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org
Subject: Re: [PATCH v2 0/2] map Fn + R key on newer Lenovo Yogas and Legions
Date: Tue, 12 Mar 2024 13:01:59 +0200 (EET) [thread overview]
Message-ID: <af3e8249-e363-46b2-9d3e-859d5e20bacf@linux.intel.com> (raw)
In-Reply-To: <f77afd46-a238-630e-e77f-2c2506097554@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
On Mon, 11 Mar 2024, Ilpo Järvinen wrote:
> On Sun, 10 Mar 2024, Gergo Koteles wrote:
>
> > This patch series adds a new KEY_REFRESH_RATE_TOGGLE input event code
> > and maps the Fn + R key to it in the ideapad-laptop driver.
> >
> > It affects two WMI keycodes. I couldn't try the 0x0a.
> >
> > Regards,
> > Gergo
> >
> > Changes in v2:
> > - use KEY_REFRESH_RATE_TOGGLE instead of KEY_FN_R
> >
> > [1]: https://lore.kernel.org/all/cover.1708399689.git.soyer@irl.hu/
> >
> > Gergo Koteles (2):
> > Input: allocate keycode for Display refresh rate toggle
> > platform/x86: ideapad-laptop: map Fn + R key to
> > KEY_REFRESH_RATE_TOGGLE
>
> As mentioned in the other thread, please redo this on top of
> pdx86/for-next.
Nevermind, I replaced the original patches with these two.
--
i.
prev parent reply other threads:[~2024-03-12 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 11:31 [PATCH v2 0/2] map Fn + R key on newer Lenovo Yogas and Legions Gergo Koteles
2024-03-10 11:31 ` [PATCH v2 1/2] Input: allocate keycode for Display refresh rate toggle Gergo Koteles
2024-03-10 21:34 ` Dmitry Torokhov
2024-03-10 11:31 ` [PATCH v2 2/2] platform/x86: ideapad-laptop: map Fn + R key to KEY_REFRESH_RATE_TOGGLE Gergo Koteles
2024-03-11 13:28 ` [PATCH v2 0/2] map Fn + R key on newer Lenovo Yogas and Legions Ilpo Järvinen
2024-03-12 11:01 ` Ilpo Järvinen [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=af3e8249-e363-46b2-9d3e-859d5e20bacf@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ike.pan@canonical.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=soyer@irl.hu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).