From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.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, robh+dt@kernel.org,
u.kleine-koenig@pengutronix.de
Subject: Re: [PATCH v2 0/2] Input: cap11xx add support for cap1203, cap1293 and cap1298
Date: Tue, 10 Jan 2023 11:22:35 +0100 [thread overview]
Message-ID: <c45a7d39-eb09-a33c-5b91-8cb1d8effaac@linaro.org> (raw)
In-Reply-To: <20230104135951.930783-1-jiriv@axis.com>
On 04/01/2023 14:59, Jiri Valek - 2N wrote:
> PATCH 1 - add compatible string for new models
> PATCH 2 - add support for new models into driver
>
Do not attach (thread) your patchsets to some other threads (unrelated
or older versions). This buries them deep in the mailbox and might
interfere with applying entire sets.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-10 10:24 UTC|newest]
Thread overview: 9+ 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 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 ` Krzysztof Kozlowski [this message]
2023-01-06 7:11 ` [PATCH " 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=c45a7d39-eb09-a33c-5b91-8cb1d8effaac@linaro.org \
--to=krzysztof.kozlowski@linaro.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=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;
as well as URLs for NNTP newsgroup(s).