linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: wangyounian@hisilicon.com
Cc: linux-media@vger.kernel.org, Sean Young <sean@mess.org>
Subject: Keymap with duplicate entries
Date: Mon, 01 Jul 2019 18:38:20 +0200	[thread overview]
Message-ID: <e06c5349efde1706c307bfaf04ace99b3bbc0375.camel@hadess.net> (raw)

Hey Younian,

There seems to be a problem in  the keymap you provided for inclusion
in the kernel.

In drivers/media/rc/keymaps/rc-hisi-poplar.c, 2 keys are triggered by
the same keycode:
 27 ↦       { 0x0000b2c5, KEY_DELETE},•
 34 ↦       { 0x0000b2c5, KEY_BACK},•

Could you please check what the correct values are for both of those
keys?

Thanks!


             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:38 Keymap with duplicate entries Bastien Nocera
2019-07-01 16:42 ` Bastien Nocera
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

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=e06c5349efde1706c307bfaf04ace99b3bbc0375.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=linux-media@vger.kernel.org \
    --cc=sean@mess.org \
    --cc=wangyounian@hisilicon.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;
as well as URLs for NNTP newsgroup(s).