From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "André Apitzsch" <git@apitzsch.eu>
Cc: Nick Dyer <nick@shmanahar.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v2 0/2] Input: atmel_mxt_ts - support capacitive keys
Date: Mon, 1 May 2023 20:23:41 -0700 [thread overview]
Message-ID: <ZFCCPcKb9xaBZQee@google.com> (raw)
In-Reply-To: <20230407-atmel_keys-v2-0-92446a4343cb@apitzsch.eu>
On Fri, Apr 07, 2023 at 02:44:23PM +0200, André Apitzsch wrote:
> Add support for touch keys found in some Atmel touch controller
> configurations.
>
> Signed-off-by: André Apitzsch <git@apitzsch.eu>
> ---
> Changes in v2:
> * Added A-b, R-b tags
Applied the lot, thank you.
>
> ---
> André Apitzsch (2):
> dt-bindings: input: atmel,maxtouch: add linux,keycodes
> Input: atmel_mxt_ts - support capacitive keys
>
> .../devicetree/bindings/input/atmel,maxtouch.yaml | 7 ++
> drivers/input/touchscreen/atmel_mxt_ts.c | 85 ++++++++++++++++++++++
> 2 files changed, 92 insertions(+)
> ---
> base-commit: f2afccfefe7be1f7346564fe619277110d341f9b
> change-id: 20230407-atmel_keys-7a49c6b677b2
>
> Best regards,
> --
> André Apitzsch <git@apitzsch.eu>
>
--
Dmitry
prev parent reply other threads:[~2023-05-02 3:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 12:44 [PATCH v2 0/2] Input: atmel_mxt_ts - support capacitive keys André Apitzsch
2023-04-07 12:44 ` [PATCH v2 1/2] dt-bindings: input: atmel,maxtouch: add linux,keycodes André Apitzsch
2023-04-07 12:44 ` [PATCH v2 2/2] Input: atmel_mxt_ts - support capacitive keys André Apitzsch
2023-05-02 3:23 ` 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=ZFCCPcKb9xaBZQee@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=git@apitzsch.eu \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@shmanahar.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.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).