From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pankaj Patil <pankaj.patil@oss.qualcomm.com>,
amitk@kernel.org, thara.gopinath@gmail.com, rafael@kernel.org,
daniel.lezcano@linaro.org, rui.zhang@intel.com,
lukasz.luba@arm.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: thermal: qcom-tsens: Document the Glymur temperature Sensor
Date: Thu, 9 Oct 2025 20:00:13 +0900 [thread overview]
Message-ID: <e9f67f33-40d5-48b7-b779-47538d48d146@kernel.org> (raw)
In-Reply-To: <20250920123631.281153-1-pankaj.patil@oss.qualcomm.com>
On 20/09/2025 21:36, Pankaj Patil wrote:
> From: Manaf Meethalavalappu Pallikunhi <quic_manafm@quicinc.com>
>
> Document the Temperature Sensor (TSENS) on Glymur Platform.
>
> Signed-off-by: Manaf Meethalavalappu Pallikunhi <quic_manafm@quicinc.com>
> Signed-off-by: Pankaj Patil <pankaj.patil@oss.qualcomm.com>
> ---
> Changes in v2:
> Fixed to sort entry in alphabetical order.
>
No, conflicting patch with Kaanapali, without any reason. Squash the
patches.
This entire split is just huge churn, huge duplication of work and quite
a lot of review put onto the community. You should have coordinated your
work better.
I am disappointed because you just don't think about the reviewing
process, about what maintainers should do with that. You just send what
was told you to send.
Explain to us - why do we want to have two 99% same patches sent the
SAME DAY, from the same company, sent in completely separate patchsets
so any simplified review will not be possible, and do same work - review
and applying - twice, instead of having only one?
Why maintainers should accept this?
Best regards,
Krzysztof
prev parent reply other threads:[~2025-10-09 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 12:36 [PATCH v2] dt-bindings: thermal: qcom-tsens: Document the Glymur temperature Sensor Pankaj Patil
2025-09-22 20:26 ` Rob Herring (Arm)
2025-10-09 11:00 ` Krzysztof Kozlowski [this message]
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=e9f67f33-40d5-48b7-b779-47538d48d146@kernel.org \
--to=krzk@kernel.org \
--cc=amitk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=pankaj.patil@oss.qualcomm.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--cc=thara.gopinath@gmail.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).