From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stanley Chu <stanley.chuys@gmail.com>,
frank.li@nxp.com, miquel.raynal@bootlin.com,
alexandre.belloni@bootlin.com, linux-i3c@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
tomer.maimon@nuvoton.com, kwliu@nuvoton.com, yschu@nuvoton.com
Subject: Re: [PATCH RESEND v2 1/4] dt-bindings: i3c: silvaco: Add npcm845 compatible string
Date: Thu, 20 Feb 2025 09:19:07 +0100 [thread overview]
Message-ID: <749d3e3c-8589-4fd8-a472-cf6b225193c8@kernel.org> (raw)
In-Reply-To: <20250220061107.1718239-2-yschu@nuvoton.com>
On 20/02/2025 07:11, Stanley Chu wrote:
> From: Stanley Chu <yschu@nuvoton.com>
>
> Add a compatible string for Nuvoton BMC NPCM845 i3c controller.
This we see from the diff. Say something useful, is it compatible with
other? Why is it in the same binding?
<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC (and consider --no-git-fallback argument, so you will
not CC people just because they made one commit years ago). It might
happen, that command when run on an older kernel, gives you outdated
entries. Therefore please be sure you base your patches on recent Linux
kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
</form letter>
>
> Signed-off-by: Stanley Chu <yschu@nuvoton.com>
> ---
> Documentation/devicetree/bindings/i3c/silvaco,i3c-master.yaml | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/i3c/silvaco,i3c-master.yaml b/Documentation/devicetree/bindings/i3c/silvaco,i3c-master.yaml
> index c56ff77677f1..9be4bc4cc482 100644
> --- a/Documentation/devicetree/bindings/i3c/silvaco,i3c-master.yaml
> +++ b/Documentation/devicetree/bindings/i3c/silvaco,i3c-master.yaml
> @@ -14,7 +14,9 @@ allOf:
>
> properties:
> compatible:
> - const: silvaco,i3c-master-v1
> + enum:
> + - silvaco,i3c-master-v1
> + - nuvoton,npcm845-i3c
Keep alphabetical order.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-20 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 6:11 [PATCH RESEND v2 0/4] Add support for Nuvoton npcm845 i3c controller Stanley Chu
2025-02-20 6:11 ` [PATCH RESEND v2 1/4] dt-bindings: i3c: silvaco: Add npcm845 compatible string Stanley Chu
2025-02-20 8:19 ` Krzysztof Kozlowski [this message]
2025-02-20 6:11 ` [PATCH RESEND v2 2/4] i3c: master: svc: Add support for Nuvoton npcm845 i3c Stanley Chu
2025-02-20 17:40 ` Frank Li
2025-02-20 6:11 ` [PATCH RESEND v2 3/4] i3c: master: svc: Fix npcm845 FIFO empty issue Stanley Chu
2025-02-20 17:56 ` Frank Li
2025-02-20 6:11 ` [PATCH RESEND v2 4/4] i3c: master: svc: Fix npcm845 invalid slvstart event Stanley Chu
2025-02-20 17:43 ` Frank Li
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=749d3e3c-8589-4fd8-a472-cf6b225193c8@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=frank.li@nxp.com \
--cc=kwliu@nuvoton.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=stanley.chuys@gmail.com \
--cc=tomer.maimon@nuvoton.com \
--cc=yschu@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;
as well as URLs for NNTP newsgroup(s).