From: Purva Yeshi <purvayeshi550@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
ukleinek@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, vz@mleia.com, piotr.wojtaszczyk@timesys.com
Cc: linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: pwm: Convert lpc32xx-pwm.txt to YAML
Date: Sat, 5 Apr 2025 01:08:59 +0530 [thread overview]
Message-ID: <b493166b-5d1b-4228-82a0-ee7efcdd03e6@gmail.com> (raw)
In-Reply-To: <023b7e98-58ef-4752-9ef4-6fe699188b2f@kernel.org>
On 02/04/25 12:03, Krzysztof Kozlowski wrote:
> On 01/04/2025 19:32, Purva Yeshi wrote:
>> On 13/03/25 16:34, Krzysztof Kozlowski wrote:
>>> On 12/03/2025 13:27, Purva Yeshi wrote:
>>>> Convert the existing `lpc32xx-pwm.txt` bindings documentation into a
>>>> YAML schema (`nxp,lpc3220-pwm.yaml`).
>>>>
>>>> Set `"#pwm-cells"` to `const: 3` for expected PWM cell properties.
>>>>
>>>> Signed-off-by: Purva Yeshi <purvayeshi550@gmail.com>
>>>> ---
>>>
>>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>>
>>>
>>> ---
>>>
>>> <form letter>
>>> This is an automated instruction, just in case, because many review tags
>>> are being ignored. If you know the process, you can skip it (please do
>>> not feel offended by me posting it here - no bad intentions intended).
>>> If you do not know the process, here is a short explanation:
>>>
>>> Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions
>>> of patchset, under or above your Signed-off-by tag, unless patch changed
>>> significantly (e.g. new properties added to the DT bindings). Tag is
>>> "received", when provided in a message replied to you on the mailing
>>> list. Tools like b4 can help here. However, there's no need to repost
>>> patches *only* to add the tags. The upstream maintainer will do that for
>>> tags received on the version they apply.
>>>
>>> Full context and explanation:
>>> https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
>>> </form letter>
>>>
>>> Best regards,
>>> Krzysztof
>>
>> Hello!
>>
>> I wanted to follow up on the patch I submitted. I was wondering if you
>> had a chance to review it and if there are any comments or feedback.
>
> And what did you quote? What's there? Did you read it before replying?
>
> Please avoid pinging during the merge window.
>
>
> Best regards,
> Krzysztof
Hello Krzysztof,
Apologies for the unnecessary follow-up. I’ll avoid pinging during the
merge window.
next prev parent reply other threads:[~2025-04-04 19:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 12:27 [PATCH v2] dt-bindings: pwm: Convert lpc32xx-pwm.txt to YAML Purva Yeshi
2025-03-12 17:59 ` Vladimir Zapolskiy
2025-03-12 22:56 ` Uwe Kleine-König
2025-03-13 3:37 ` Vladimir Zapolskiy
2025-03-13 7:22 ` Uwe Kleine-König
2025-03-13 11:04 ` Krzysztof Kozlowski
2025-03-13 14:25 ` Purva Yeshi
2025-04-01 17:32 ` Purva Yeshi
2025-04-02 6:33 ` Krzysztof Kozlowski
2025-04-04 19:38 ` Purva Yeshi [this message]
2025-04-03 10:41 ` Uwe Kleine-König
2025-04-04 19:42 ` Purva Yeshi
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=b493166b-5d1b-4228-82a0-ee7efcdd03e6@gmail.com \
--to=purvayeshi550@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=piotr.wojtaszczyk@timesys.com \
--cc=robh@kernel.org \
--cc=ukleinek@kernel.org \
--cc=vz@mleia.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