From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Ping Cheng <pinglinux@gmail.com>, Kamil Debski <kamil@wypas.org>,
Hans Verkuil <hans.verkuil@cisco.com>
Cc: linux-input@vger.kernel.org, jkosina@suse.cz,
Ping Cheng <pingc@wacom.com>, Ping Cheng <ping.cheng@wacom.com>
Subject: Re: [PATCH] HID: change KEY_DATA from 0x275 to 0x277
Date: Mon, 28 Nov 2016 13:20:36 -0800 [thread overview]
Message-ID: <20161128212036.GA37762@dtor-ws> (raw)
In-Reply-To: <1480366164-18706-1-git-send-email-pingc@wacom.com>
On Mon, Nov 28, 2016 at 12:49:24PM -0800, Ping Cheng wrote:
> 0x275 is used by KEY_FASTREVERSE. Or, was that on purpose to use
> the same value as KEY_FASTREVERSE for KEY_DATA?
>
> Signed-off-by: Ping Cheng <ping.cheng@wacom.com>
Ugh, that's not good. I guess we should indeed change this and make sure
it goes to stable.
Hans, Kamil, I do not suppose anyone actually been using KEY_DATA as it
would have been clashing with KEY_FASTREVERSE?
Thanks.
> ---
> include/uapi/linux/input-event-codes.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/input-event-codes.h b/include/uapi/linux/input-event-codes.h
> index d6d071f..3af60ee 100644
> --- a/include/uapi/linux/input-event-codes.h
> +++ b/include/uapi/linux/input-event-codes.h
> @@ -640,7 +640,7 @@
> * Control a data application associated with the currently viewed channel,
> * e.g. teletext or data broadcast application (MHEG, MHP, HbbTV, etc.)
> */
> -#define KEY_DATA 0x275
> +#define KEY_DATA 0x277
>
> #define BTN_TRIGGER_HAPPY 0x2c0
> #define BTN_TRIGGER_HAPPY1 0x2c0
> --
> 2.7.4
>
--
Dmitry
next prev parent reply other threads:[~2016-11-28 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 20:49 [PATCH] HID: change KEY_DATA from 0x275 to 0x277 Ping Cheng
2016-11-28 21:20 ` Dmitry Torokhov [this message]
2016-11-29 7:09 ` Hans Verkuil
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=20161128212036.GA37762@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=hans.verkuil@cisco.com \
--cc=jkosina@suse.cz \
--cc=kamil@wypas.org \
--cc=linux-input@vger.kernel.org \
--cc=ping.cheng@wacom.com \
--cc=pingc@wacom.com \
--cc=pinglinux@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.