From: Jiri Valek - 2N <jiriv@axis.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: "Jiri Valek - 2N" <jiriv@axis.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"open list:INPUT (KEYBOARD, MOUSE, JOYSTICK,
TOUCHSCREEN)..." <linux-input@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] Input: cap11xx add support for cap1203, cap1293 and cap1298
Date: Tue, 3 Jan 2023 14:41:02 +0100 [thread overview]
Message-ID: <20230103134105.736346-1-jiriv@axis.com> (raw)
PATCH 1 - add compatible string for new models
PATCH 2 - add support for new models into driver
Jiri Valek - 2N (2):
dt-bindings: input: microchip,cap11xx: add cap1203, cap1293 and
cap1298
Input: cap11xx - add support for cap1203, cap1293 and cap1298
.../bindings/input/microchip,cap11xx.yaml | 3 +++
drivers/input/keyboard/cap11xx.c | 20 +++++++++++++++++--
2 files changed, 21 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2023-01-03 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 13:41 Jiri Valek - 2N [this message]
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
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
2023-01-06 7:11 ` [PATCH 2/2] Input: cap11xx - " 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=20230103134105.736346-1-jiriv@axis.com \
--to=jiriv@axis.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzysztof.kozlowski+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®