From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Guido Günther" <agx@sigxcpu.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Hermes Zhang <chenhuiz@axis.com>,
Tony Lindgren <tony@atomide.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
phone-devel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] Input: gpio-keys - expose wakeup keys in sysfs
Date: Mon, 13 May 2024 14:35:22 +0200 [thread overview]
Message-ID: <CAMuHMdVcR_3HcQzQse+5-2dgC4iLzFyiFO=ifR0hxymWRjURLQ@mail.gmail.com> (raw)
In-Reply-To: <2b6eb6c3f68509aa35cdf2e2a586689ae97681ab.1715255980.git.agx@sigxcpu.org>
Hi Guido,
On Thu, May 9, 2024 at 2:00 PM Guido Günther <agx@sigxcpu.org> wrote:
> This helps user space to figure out which keys should be used to unidle a
> device. E.g on phones the volume rocker should usually not unblank the
> screen.
>
> Signed-off-by: Guido Günther <agx@sigxcpu.org>
Thanks for your patch!
This is indeed a useful feature.
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-05-13 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1715255980.git.agx@sigxcpu.org>
2024-05-09 12:00 ` [PATCH v1 1/1] Input: gpio-keys - expose wakeup keys in sysfs Guido Günther
2024-05-13 12:35 ` Geert Uytterhoeven [this message]
2024-05-13 22:13 ` Dmitry Torokhov
2024-05-14 16:05 ` Guido Günther
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='CAMuHMdVcR_3HcQzQse+5-2dgC4iLzFyiFO=ifR0hxymWRjURLQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=agx@sigxcpu.org \
--cc=chenhuiz@axis.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=tony@atomide.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).