From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org
Subject: Re: [PATCH] ARM: tegra: convert device tree files to use key defines
Date: Thu, 12 Dec 2013 13:08:35 -0700 [thread overview]
Message-ID: <52AA17C3.5050700@wwwdotorg.org> (raw)
In-Reply-To: <1385989797-10879-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 12/02/2013 06:09 AM, Laxman Dewangan wrote:
> Use key code macros for all key code refernced for keys.
>
> For tegra20-seaboard.dts and tegra20-harmony.dts:
> The key comment for key (16th row and 1st column) is KEY_KPSLASH but
> code is 0x004e which is the key code for KEY_KPPLUS. As there other
> key exist with KY_KPPLUS, I am assuming key code is wrong and comment
> is fine. With this assumption, I am keeping the key code as KEY_KPSLASH.
I've applied this to Tegra's for-3.14/dt branch.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: convert device tree files to use key defines
Date: Thu, 12 Dec 2013 13:08:35 -0700 [thread overview]
Message-ID: <52AA17C3.5050700@wwwdotorg.org> (raw)
In-Reply-To: <1385989797-10879-1-git-send-email-ldewangan@nvidia.com>
On 12/02/2013 06:09 AM, Laxman Dewangan wrote:
> Use key code macros for all key code refernced for keys.
>
> For tegra20-seaboard.dts and tegra20-harmony.dts:
> The key comment for key (16th row and 1st column) is KEY_KPSLASH but
> code is 0x004e which is the key code for KEY_KPPLUS. As there other
> key exist with KY_KPPLUS, I am assuming key code is wrong and comment
> is fine. With this assumption, I am keeping the key code as KEY_KPSLASH.
I've applied this to Tegra's for-3.14/dt branch.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: rob.herring@calxeda.com, mark.rutland@arm.com,
thierry.reding@gmail.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@arm.linux.org.uk, ijc+devicetree@hellion.org.uk
Subject: Re: [PATCH] ARM: tegra: convert device tree files to use key defines
Date: Thu, 12 Dec 2013 13:08:35 -0700 [thread overview]
Message-ID: <52AA17C3.5050700@wwwdotorg.org> (raw)
In-Reply-To: <1385989797-10879-1-git-send-email-ldewangan@nvidia.com>
On 12/02/2013 06:09 AM, Laxman Dewangan wrote:
> Use key code macros for all key code refernced for keys.
>
> For tegra20-seaboard.dts and tegra20-harmony.dts:
> The key comment for key (16th row and 1st column) is KEY_KPSLASH but
> code is 0x004e which is the key code for KEY_KPPLUS. As there other
> key exist with KY_KPPLUS, I am assuming key code is wrong and comment
> is fine. With this assumption, I am keeping the key code as KEY_KPSLASH.
I've applied this to Tegra's for-3.14/dt branch.
next prev parent reply other threads:[~2013-12-12 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 13:09 [PATCH] ARM: tegra: convert device tree files to use key defines Laxman Dewangan
2013-12-02 13:09 ` Laxman Dewangan
2013-12-02 13:09 ` Laxman Dewangan
2013-12-03 20:04 ` Stephen Warren
2013-12-03 20:04 ` Stephen Warren
2013-12-04 5:47 ` Laxman Dewangan
2013-12-04 5:47 ` Laxman Dewangan
[not found] ` <1385989797-10879-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-12-12 20:08 ` Stephen Warren [this message]
2013-12-12 20:08 ` Stephen Warren
2013-12-12 20:08 ` Stephen Warren
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=52AA17C3.5050700@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.