From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Jeff LaBundy <jeff@labundy.com>,
dmitry.torokhov@gmail.com, robh+dt@kernel.org
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
jeff@labundy.com
Subject: Re: [PATCH v3 0/7] Additional fixes for Azoteq IQS7222A/B/C
Date: Fri, 28 Oct 2022 09:56:37 +0200 [thread overview]
Message-ID: <87pmectm8a.fsf@baylibre.com> (raw)
In-Reply-To: <Y1SQ2t6yUvdaIQPG@nixie71>
On sam., oct. 22, 2022 at 19:54, Jeff LaBundy <jeff@labundy.com> wrote:
> This series comprises a second round of fixes that result from
> continued testing and updated guidance from the vendor.
>
> Jeff LaBundy (7):
> Input: iqs7222 - drop unused device node references
> dt-bindings: input: iqs7222: Reduce 'linux,code' to optional
> Input: iqs7222 - report malformed properties
> dt-bindings: input: iqs7222: Correct minimum slider size
> Input: iqs7222 - protect against undefined slider size
> dt-bindings: input: iqs7222: Add support for IQS7222A v1.13+
> Input: iqs7222 - add support for IQS7222A v1.13+
>
> .../bindings/input/azoteq,iqs7222.yaml | 25 +-
> drivers/input/misc/iqs7222.c | 504 +++++++++++-------
> 2 files changed, 311 insertions(+), 218 deletions(-)
Not sure this requires a re-send, but the series seems ill-formatted.
all patches are posted separately to the list instead of replying to the
cover letter. Is that expected?
>
> --
> 2.34.1
next prev parent reply other threads:[~2022-10-28 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 0:54 [PATCH v3 0/7] Additional fixes for Azoteq IQS7222A/B/C Jeff LaBundy
2022-10-28 7:56 ` Mattijs Korpershoek [this message]
2022-10-28 13:25 ` Jeff LaBundy
2022-10-28 16:14 ` Dmitry Torokhov
2022-11-02 4:58 ` Jeff LaBundy
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=87pmectm8a.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jeff@labundy.com \
--cc=linux-input@vger.kernel.org \
--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).