From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Matt Ranostay <mranostay@ti.com>,
nm@ti.com, vigneshr@ti.com, krzysztof.kozlowski+dt@linaro.org,
robh+dt@kernel.org, lee@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH RESEND v2 2/2] arm64: dts: k3-j72*: correct compatible for syscon entries
Date: Wed, 26 Oct 2022 10:49:09 -0400 [thread overview]
Message-ID: <64a01388-aa53-d88a-b6fe-4a935a299358@linaro.org> (raw)
In-Reply-To: <20221024035405.366208-3-mranostay@ti.com>
On 23/10/2022 23:54, Matt Ranostay wrote:
> Add missing ti,j7*-system-controller compatible to bus defines in mcu/wakeup
> domains to avoid the following similar warnings from dt-schema checks:
>
> arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dtb: syscon@40f00000: compatible: ['syscon', 'simple-mfd'] is too short'
>
This is a friendly reminder during the review process.
It looks like you received a tag and forgot to add it.
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. However, there's no need to repost patches *only* to add the
tags. The upstream maintainer will do that for acks received on the
version they apply.
https://elixir.bootlin.com/linux/v5.17/source/Documentation/process/submitting-patches.rst#L540
If a tag was not added on purpose, please state why and what changed.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-10-26 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 3:54 [PATCH RESEND v2 0/2] arm64: dts: add new compatibles for J7 platforms Matt Ranostay
2022-10-24 3:54 ` [PATCH RESEND v2 1/2] dt-bindings: mfd: ti,j721e-system-controller: add compatible strings for other platforms Matt Ranostay
2022-10-25 22:55 ` Rob Herring
2022-10-26 14:48 ` Krzysztof Kozlowski
2022-10-31 15:29 ` Lee Jones
2022-10-24 3:54 ` [PATCH RESEND v2 2/2] arm64: dts: k3-j72*: correct compatible for syscon entries Matt Ranostay
2022-10-26 14:49 ` 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=64a01388-aa53-d88a-b6fe-4a935a299358@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mranostay@ti.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).