From: Rob Herring <robh@kernel.org>
To: Jiri Valek - 2N <jiriv@axis.com>
Cc: devicetree@vger.kernel.org, dmitry.torokhov@gmail.com,
krzysztof.kozlowski+dt@linaro.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, u.kleine-koenig@pengutronix.de
Subject: Re: [PATCH v2 1/2] dt-bindings: input: microchip,cap11xx: add cap1203, cap1293 and cap1298
Date: Sun, 8 Jan 2023 15:43:57 -0600 [thread overview]
Message-ID: <20230108214357.GA318729-robh@kernel.org> (raw)
In-Reply-To: <20230104135951.930783-2-jiriv@axis.com>
On Wed, Jan 04, 2023 at 02:59:50PM +0100, Jiri Valek - 2N wrote:
> Add support for cap1203, cap1293 and cap1298.
>
> Signed-off-by: Jiri Valek - 2N <jiriv@axis.com>
> ---
> Documentation/devicetree/bindings/input/microchip,cap11xx.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/input/microchip,cap11xx.yaml b/Documentation/devicetree/bindings/input/microchip,cap11xx.yaml
> index 67d4d8f86a2d..08ca993b94c4 100644
> --- a/Documentation/devicetree/bindings/input/microchip,cap11xx.yaml
> +++ b/Documentation/devicetree/bindings/input/microchip,cap11xx.yaml
> @@ -20,6 +20,9 @@ properties:
> - microchip,cap1126
> - microchip,cap1188
> - microchip,cap1206
> + - microchip,cap1203
> + - microchip,cap1293
> + - microchip,cap1298
Maintain alphabetical order please.
>
> reg:
> maxItems: 1
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2023-01-08 21:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 13:41 [PATCH 0/2] Input: cap11xx add support for cap1203, cap1293 and cap1298 Jiri Valek - 2N
2023-01-03 13:41 ` [PATCH 1/2] dt-bindings: input: microchip,cap11xx: add " Jiri Valek - 2N
2023-01-03 13:41 ` [PATCH 2/2] Input: cap11xx - add support for " Jiri Valek - 2N
2023-01-04 4:37 ` kernel test robot
2023-01-04 13:59 ` [PATCH v2 0/2] Input: cap11xx " Jiri Valek - 2N
2023-01-04 13:59 ` [PATCH v2 1/2] dt-bindings: input: microchip,cap11xx: add " Jiri Valek - 2N
2023-01-08 21:43 ` Rob Herring [this message]
2023-01-04 13:59 ` [PATCH v2 2/2] Input: cap11xx - add support for " Jiri Valek - 2N
2023-01-10 10:22 ` [PATCH v2 0/2] Input: cap11xx " Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2023-01-05 16:47 [PATCH 2/2] Input: cap11xx - " kernel test robot
2023-01-06 7:11 ` Dan Carpenter
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=20230108214357.GA318729-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jiriv@axis.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.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.