From: Zhang Heng <zhangheng@kylinos.cn>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: cryolitia.pukngae@linux.dev, kees+treewide@kernel.org,
DongLin_Lyu@outlook.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: atkbd - rate-limit unknown key warnings
Date: Tue, 22 Sep 2026 10:12:15 +0800 [thread overview]
Message-ID: <3aa95d2e-9398-482a-8bd5-876ef1e2ce89@kylinos.cn> (raw)
In-Reply-To: <arFZdtgmZXcK9k1V@google.com>
Thanks for your reply. This fix should be handled in userspace. It’s
just that for ordinary users, they see a lot of warning messages after
pressing keys, so perhaps it would be better to limit the output. I also
agree with you that this patch is not necessary—after all, the benefit
of this patch is indeed limited. If the patch is not merged, I’m fine
with that.
next prev parent reply other threads:[~2026-09-22 2:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 13:19 Zhang Heng
2026-09-21 16:40 ` Dmitry Torokhov
2026-09-22 2:12 ` Zhang Heng [this message]
2026-09-22 3:38 ` Dmitry Torokhov
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=3aa95d2e-9398-482a-8bd5-876ef1e2ce89@kylinos.cn \
--to=zhangheng@kylinos.cn \
--cc=DongLin_Lyu@outlook.com \
--cc=cryolitia.pukngae@linux.dev \
--cc=dmitry.torokhov@gmail.com \
--cc=kees+treewide@kernel.org \
--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
all inboxes | Powered by JetHome®