From: Jiri Valek - 2N <jiriv@axis.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<krzysztof.kozlowski+dt@linaro.org>, <dmitry.torokhov@gmail.com>
Cc: <devicetree@vger.kernel.org>, <linux-input@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <robh+dt@kernel.org>,
<u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH v2 2/2] Input: cap11xx - add advanced sensitivity settings
Date: Mon, 26 Jun 2023 15:16:57 +0200 [thread overview]
Message-ID: <d45cbede-dfd0-baf4-d64d-e5ed6425d342@axis.com> (raw)
In-Reply-To: <a980885a-3379-9278-2652-1a1b68983709@linaro.org>
On 6/26/23 14:37, Krzysztof Kozlowski wrote:
> On 26/06/2023 13:37, Jiri Valek - 2N wrote:
>> Add support for advanced sensitivity settings that allows more precise
>> tunig of touch buttons. Input-treshold allows to set the sensitivity for
>> each channel separately. Also add signal guard feature for CAP129x chips.
>>
>> Reviewed-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>
> NAK. Stop adding fake entries.
>
> Best regards,
> Krzysztof
>
Sorry to you and also to Dmitry, I incorrectly used "Reviewed-by" tag.
I wanted to add Dmitry as reviewer and give him some credits.
I hope that "Reported-by" is better, but I'd rather put no tags.
BR
Jiri
prev parent reply other threads:[~2023-06-26 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 11:37 [PATCH v2 0/2] Input: cap11xx add advanced sensitivity settings Jiri Valek - 2N
2023-06-26 11:37 ` [PATCH v2 1/2] dt-bindings: input: microchip,cap11xx: " Jiri Valek - 2N
2023-06-26 12:36 ` Krzysztof Kozlowski
2023-06-26 12:41 ` Krzysztof Kozlowski
2023-06-26 13:14 ` Jiri Valek - 2N
2023-06-26 13:16 ` Krzysztof Kozlowski
2023-06-26 11:37 ` [PATCH v2 2/2] Input: cap11xx - " Jiri Valek - 2N
2023-06-26 12:37 ` Krzysztof Kozlowski
2023-06-26 13:16 ` Jiri Valek - 2N [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=d45cbede-dfd0-baf4-d64d-e5ed6425d342@axis.com \
--to=jiriv@axis.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.