[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=XjzBLTPMqOf1NK0pjXiZWrLT227nksxhMqaFG6GxAqjQ@mail.gmail.com>
Date: Wed, 6 Jan 2021 17:16:10 -0800
From: Doug Anderson <dianders@...omium.org>
To: Stephen Boyd <swboyd@...omium.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Enric Balletbo i Serra <enric.balletbo@...labora.com>,
Benson Leung <bleung@...omium.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
"open list:HID CORE LAYER" <linux-input@...r.kernel.org>,
Guenter Roeck <groeck@...omium.org>
Subject: Re: [PATCH] Input: cros_ec_keyb: Add support for a front proximity switch
Hi,
On Fri, Dec 4, 2020 at 4:48 PM Stephen Boyd <swboyd@...omium.org> wrote:
>
> Some cros ECs support a front proximity MKBP event via
> 'EC_MKBP_FRONT_PROXIMITY'. Map this to the 'SW_FRONT_PROXIMITY' input
> event code so it can be reported up to userspace.
>
> Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>
> Cc: Benson Leung <bleung@...omium.org>
> Cc: Guenter Roeck <groeck@...omium.org>
> Signed-off-by: Stephen Boyd <swboyd@...omium.org>
> ---
> drivers/input/keyboard/cros_ec_keyb.c | 5 +++++
> include/linux/platform_data/cros_ec_commands.h | 1 +
> 2 files changed, 6 insertions(+)
This seems really straightforward.
Reviewed-by: Douglas Anderson <dianders@...omium.org>
Given that it touches a header file owned by the Chrome OS maintainers
and a driver owned by input, how should it land? One maintainer Acks
and the other lands?
-Doug
Powered by blists - more mailing lists