From: Rob Herring <robh@kernel.org>
To: Philip Chen <philipchen@chromium.org>
Cc: Benson Leung <bleung@chromium.org>,
Rob Herring <robh+dt@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
dmitry.torokhov@gmail.com, swboyd@chromium.org,
devicetree@vger.kernel.org,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
dianders@chromium.org
Subject: Re: [PATCH v6 3/3] dt-bindings: input: Fix the keymap for LOCK key
Date: Fri, 5 Feb 2021 15:13:47 -0600 [thread overview]
Message-ID: <20210205211347.GA3752072@robh.at.kernel.org> (raw)
In-Reply-To: <20210115143555.v6.3.I96134907488f41f358d03f3c1b08194f9547e670@changeid>
On Fri, 15 Jan 2021 14:36:17 -0800, Philip Chen wrote:
> Decouple LOCK from F13 and directly map the LOCK key (KSI3/KSO9) to
> KEY_SLEEP action key code.
>
> Signed-off-by: Philip Chen <philipchen@chromium.org>
> ---
>
> Changes in v6:
> - New patch in v6
>
> include/dt-bindings/input/cros-ec-keyboard.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-02-05 21:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 22:36 [PATCH v6 1/3] dt-bindings: input: Create macros for cros-ec keymap Philip Chen
2021-01-15 22:36 ` [PATCH v6 2/3] ARM: dts: cros-ec-keyboard: Use keymap macros Philip Chen
2021-01-15 22:38 ` Stephen Boyd
2021-02-23 5:39 ` Dmitry Torokhov
2021-01-15 22:36 ` [PATCH v6 3/3] dt-bindings: input: Fix the keymap for LOCK key Philip Chen
2021-01-15 22:39 ` Stephen Boyd
2021-02-04 23:59 ` Philip Chen
2021-02-05 21:13 ` Rob Herring [this message]
2021-02-23 5:39 ` Dmitry Torokhov
2021-01-15 22:38 ` [PATCH v6 1/3] dt-bindings: input: Create macros for cros-ec keymap Stephen Boyd
2021-01-15 22:59 ` Philip Chen
2021-01-20 15:49 ` Rob Herring
2021-02-23 5:39 ` 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=20210205211347.GA3752072@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philipchen@chromium.org \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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).