From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Ike Panhc <ike.pan@canonical.com>,
Hans de Goede <hdegoede@redhat.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Philipp Jungkamp <p.jungkamp@gmx.net>,
Gergo Koteles <soyer@irl.hu>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 0/2] map Fn + R key on newer Yogas and Legions
Date: Mon, 26 Feb 2024 15:27:33 +0200 [thread overview]
Message-ID: <170895405312.2243.4199399921923370447.b4-ty@linux.intel.com> (raw)
In-Reply-To: <cover.1708399689.git.soyer@irl.hu>
On Tue, 20 Feb 2024 04:39:34 +0100, Gergo Koteles wrote:
> This patch series adds a new KEY_FN_R input event code and map the
> Fn + R key to it in the ideapad-laptop driver.
>
> It affects two WMI keycodes and I couldn't try the 0x0a, but I couldn't
> find any indication that the refresh rate toggle should not be Fn + R.
>
> Regards,
> Gergo
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo branch. Note it will show up in the public
platform-drivers-x86/review-ilpo branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/2] Input: allocate keycode for Fn + R
commit: 4e45fa464aeef4e803412b5dcce73aad48c94b0e
[2/2] platform/x86: ideapad-laptop: map Fn + R key to KEY_FN_R
commit: cd4525993e49f1449e9380bd28fa1179b05c911d
--
i.
next prev parent reply other threads:[~2024-02-26 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 3:39 Gergo Koteles
2024-02-20 3:39 ` [PATCH 1/2] Input: allocate keycode for Fn + R Gergo Koteles
2024-02-20 3:39 ` [PATCH 2/2] platform/x86: ideapad-laptop: map Fn + R key to KEY_FN_R Gergo Koteles
2024-02-26 13:27 ` Ilpo Järvinen [this message]
2024-03-10 1:39 ` [PATCH 0/2] map Fn + R key on newer Yogas and Legions Dmitry Torokhov
2024-03-11 10:53 ` Ilpo Järvinen
2024-03-11 18:45 ` Dmitry Torokhov
2024-03-12 11:01 ` Ilpo Järvinen
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=170895405312.2243.4199399921923370447.b4-ty@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=p.jungkamp@gmx.net \
--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
all inboxes | Powered by JetHome®