From: Bastien Nocera <hadess@hadess.net>
To: aet@rasterburn.org
Cc: linux-media@vger.kernel.org, Sean Young <sean@mess.org>
Subject: Keymap with duplicate entries
Date: Mon, 01 Jul 2019 18:38:23 +0200 [thread overview]
Message-ID: <e02bb1c0552601c75fd4971c7b56755fb8e7c241.camel@hadess.net> (raw)
Hey Aapo,
There seems to be a problem in the keymap you provided for inclusion
in the kernel.
In drivers/media/usb/dvb-usb/m920x.c, 2 keys are triggered by the same
keycode:
790 ↦ { 0x08, KEY_SUBTITLE },•
794 ↦ { 0x08, KEY_VIDEO },↦ ↦ /* A/V */•
Could you please check what the correct values are for both of those
keys?
Thanks!
next reply other threads:[~2019-07-01 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 16:38 Bastien Nocera [this message]
2019-07-01 16:42 ` Keymap with duplicate entries Bastien Nocera
-- strict thread matches above, loose matches on Subject: below --
2019-07-01 16:38 Bastien Nocera
2019-07-02 22:29 ` Malcolm Priestley
2019-07-03 9:23 ` Sean Young
2019-07-03 20:41 ` Malcolm Priestley
2019-07-01 16:38 Bastien Nocera
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=e02bb1c0552601c75fd4971c7b56755fb8e7c241.camel@hadess.net \
--to=hadess@hadess.net \
--cc=aet@rasterburn.org \
--cc=linux-media@vger.kernel.org \
--cc=sean@mess.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;
as well as URLs for NNTP newsgroup(s).