From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chi-Wen Weng <cwweng.linux@gmail.com>,
ukleinek@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, linux-pwm@vger.kernel.org,
devicetree@vger.kernel.org, ychuang3@nuvoton.com,
schung@nuvoton.com, cwweng@nuvoton.com
Subject: Re: [PATCH RESEND v2 1/2] dt-bindings: pwm: nuvoton: Add MA35D1 pwm
Date: Thu, 24 Oct 2024 13:18:46 +0200 [thread overview]
Message-ID: <204ad774-a41a-4c3a-bb6c-57e180608341@kernel.org> (raw)
In-Reply-To: <20241024104309.169510-2-cwweng.linux@gmail.com>
On 24/10/2024 12:43, Chi-Wen Weng wrote:
> Add dt-bindings for Nuvoton MA35D1 SoC PWM controller.
>
> Signed-off-by: Chi-Wen Weng <cwweng.linux@gmail.com>
> ---
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
<form letter>
Please add Acked-by/Reviewed-by/Tested-by tags when posting new
versions, under or above your Signed-off-by tag. 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.
https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577
</form letter>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-24 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 10:43 [PATCH RESEND v2 0/2] Add support for nuvoton ma35d1 pwm controller Chi-Wen Weng
2024-10-24 10:43 ` [PATCH RESEND v2 1/2] dt-bindings: pwm: nuvoton: Add MA35D1 pwm Chi-Wen Weng
2024-10-24 11:18 ` Krzysztof Kozlowski [this message]
2024-10-24 10:43 ` [PATCH RESEND v2 2/2] pwm: Add Nuvoton MA35D1 PWM controller support Chi-Wen Weng
2024-11-20 16:49 ` Trevor Gamblin
2024-11-20 22:03 ` Uwe Kleine-König
2024-12-06 5:58 ` Chi-Wen Weng
2024-12-06 5:56 ` Chi-Wen Weng
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=204ad774-a41a-4c3a-bb6c-57e180608341@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cwweng.linux@gmail.com \
--cc=cwweng@nuvoton.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=schung@nuvoton.com \
--cc=ukleinek@kernel.org \
--cc=ychuang3@nuvoton.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