From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yasin Lee <yasin.lee.x@outlook.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, Yasin Lee <yasin.lee.x@gmail.com>
Subject: Re: [PATCH v5 2/3] dt-bindings:iio:proximity: Add hx9023s binding
Date: Sun, 16 Jun 2024 09:42:57 +0200 [thread overview]
Message-ID: <2146cc14-dd70-4f49-9667-1564fc6a37dc@kernel.org> (raw)
In-Reply-To: <SN7PR12MB810142C58543160AB45D07B3A4CC2@SN7PR12MB8101.namprd12.prod.outlook.com>
On 16/06/2024 09:36, Yasin Lee wrote:
> From: Yasin Lee <yasin.lee.x@gmail.com>
>
> A capacitive proximity sensor
Not much improved. No changelog, no responses to previous comments.
I already asked TWICE. So this is third time. Respond to each comment
and acknowledge that you are going to implement it.
Then write full changelog in patch changelog (so under ---) or in cover
letter (not present here) saying what changed.
NAK, because you keep ignoring same comments given over and over.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-16 7:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240616-add-tyhx-hx9023s-sensor-driver-v5-0-ebaf280bbf0e@outlook.com>
2024-06-16 7:36 ` [PATCH v5 1/3] dt-bindings:iio:proximity:new vendor prefix: tyhx Yasin Lee
2024-06-16 7:43 ` Krzysztof Kozlowski
2024-06-18 15:50 ` Yasin Lee
2024-06-16 7:36 ` [PATCH v5 2/3] dt-bindings:iio:proximity: Add hx9023s binding Yasin Lee
2024-06-16 7:42 ` Krzysztof Kozlowski [this message]
2024-06-18 15:36 ` Yasin Lee
2024-06-16 8:40 ` Rob Herring (Arm)
2024-06-17 14:51 ` Yasin Lee
2024-06-16 7:36 ` [PATCH v5 3/3] iio:proximity:hx9023s: Add TYHX HX9023S sensor driver Yasin Lee
2024-06-17 11:34 ` kernel test robot
2024-06-17 19:22 ` Jonathan Cameron
2024-06-18 12:05 ` Yasin Lee
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=2146cc14-dd70-4f49-9667-1564fc6a37dc@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=yasin.lee.x@gmail.com \
--cc=yasin.lee.x@outlook.com \
/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).