From: Kaustabh Chakraborty <kauschluss@disroot.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
devicetree@vger.kernel.org,
Kaustabh Chakraborty <kauschluss@disroot.org>
Subject: Re: [PATCH v2 2/3] mfd: sec: add support for S2MPU05 PMIC
Date: Wed, 26 Feb 2025 01:36:14 +0530 [thread overview]
Message-ID: <32c8a624fc44d048e90f556ab293d43d@disroot.org> (raw)
In-Reply-To: <b150ef5e-08b3-4747-8fd3-7b60410513a1@kernel.org>
On 2025-02-26 00:14, Krzysztof Kozlowski wrote:
>>> BTW, what happened with all the review tags? Nothing in cover letter nor
>>> changelog explains dropping reviews.
>>
>> Haven't explicitly mentioned dropping the tags, but I've changed the
>> macros a bit, among other things (which is mentioned in cover). I assume
>> that's the standard procedure.
>
>
> No, it is highly nonstandard. You must mention dropping tags and
> submitting-patches explicitly asks for that.
Then I might've missed it, apologies. Will mention in changelog in v3.
next prev parent reply other threads:[~2025-02-25 20:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 18:49 [PATCH v2 0/3] Introduce support for Exynos7870's S2MPU05 PMIC and its regulators Kaustabh Chakraborty
2025-02-18 18:49 ` [PATCH v2 1/3] regulator: dt-bindings: add documentation for s2mpu05-pmic regulators Kaustabh Chakraborty
2025-02-23 10:38 ` Krzysztof Kozlowski
2025-02-18 18:49 ` [PATCH v2 2/3] mfd: sec: add support for S2MPU05 PMIC Kaustabh Chakraborty
2025-02-23 10:40 ` Krzysztof Kozlowski
2025-02-24 17:37 ` Kaustabh Chakraborty
2025-02-24 19:18 ` Krzysztof Kozlowski
2025-02-25 18:14 ` Kaustabh Chakraborty
2025-02-25 18:44 ` Krzysztof Kozlowski
2025-02-25 20:06 ` Kaustabh Chakraborty [this message]
2025-02-18 18:49 ` [PATCH v2 3/3] regulator: s2mps11: Add support for S2MPU05 regulators Kaustabh Chakraborty
2025-02-23 10:42 ` Krzysztof Kozlowski
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=32c8a624fc44d048e90f556ab293d43d@disroot.org \
--to=kauschluss@disroot.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh@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