linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mathew King <mathewk@chromium.org>
Cc: linux-kernel@vger.kernel.org, Rajat Jain <rajatja@google.com>,
	Sean Paul <seanpaul@chromium.org>,
	Jesse Barnes <jsbarnes@google.com>,
	Duncan Laurie <dlaurie@google.com>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] input: Add privacy screen toggle keycode
Date: Wed, 4 Dec 2019 17:28:21 -0800	[thread overview]
Message-ID: <20191205012821.GO50317@dtor-ws> (raw)
In-Reply-To: <20191017163208.235518-1-mathewk@chromium.org>

On Thu, Oct 17, 2019 at 10:32:08AM -0600, Mathew King wrote:
> Add keycode for toggling electronic privacy screen to the keycodes
> definition. Some new laptops have a privacy screen which can be toggled
> with a key on the keyboard.
> 
> Signed-off-by: Mathew King <mathewk@chromium.org>

Applied, thank you.

> ---
>  include/uapi/linux/input-event-codes.h | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/include/uapi/linux/input-event-codes.h b/include/uapi/linux/input-event-codes.h
> index 85387c76c24f..05d8b4f4f82f 100644
> --- a/include/uapi/linux/input-event-codes.h
> +++ b/include/uapi/linux/input-event-codes.h
> @@ -649,6 +649,8 @@
>   */
>  #define KEY_DATA			0x277
>  #define KEY_ONSCREEN_KEYBOARD		0x278
> +/* Electronic privacy screen control */
> +#define KEY_PRIVACY_SCREEN_TOGGLE	0x279
>  
>  #define BTN_TRIGGER_HAPPY		0x2c0
>  #define BTN_TRIGGER_HAPPY1		0x2c0
> -- 
> 2.23.0.700.g56cf767bdb-goog
> 

-- 
Dmitry

      parent reply	other threads:[~2019-12-05  1:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 16:32 [PATCH] input: Add privacy screen toggle keycode Mathew King
2019-10-17 16:37 ` Dmitry Torokhov
2019-12-05  1:28 ` Dmitry Torokhov [this message]

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=20191205012821.GO50317@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=dlaurie@google.com \
    --cc=jsbarnes@google.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathewk@chromium.org \
    --cc=rajatja@google.com \
    --cc=seanpaul@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).