From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Rob Herring <robh@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: interrrupt-controller: uniphier-aidet: Use unevaluatedProperties
Date: Fri, 15 Apr 2022 10:17:25 +0900 [thread overview]
Message-ID: <2005f406-0117-b0eb-cc4b-2a921cf6528c@socionext.com> (raw)
In-Reply-To: <Ylcf0QOBAne6fKQr@robh.at.kernel.org>
Hi Rob,
On 2022/04/14 4:09, Rob Herring wrote:
> On Thu, Apr 07, 2022 at 04:47:44PM +0900, Kunihiko Hayashi wrote:
>> This refers common bindings, so this is preferred for
>> unevaluatedProperties instead of additionalProperties.
>>
>> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
>> ---
>> .../bindings/interrupt-controller/socionext,uniphier-aidet.yaml | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git
> a/Documentation/devicetree/bindings/interrupt-controller/socionext,uniphie
> r-aidet.yaml
> b/Documentation/devicetree/bindings/interrupt-controller/socionext,uniphie
> r-aidet.yaml
>> index f89ebde76dab..77f2d58a9c3f 100644
>> ---
> a/Documentation/devicetree/bindings/interrupt-controller/socionext,uniphie
> r-aidet.yaml
>> +++
> b/Documentation/devicetree/bindings/interrupt-controller/socionext,uniphie
> r-aidet.yaml
>> @@ -49,7 +49,7 @@ required:
>> - interrupt-controller
>> - '#interrupt-cells'
>>
>> -additionalProperties: false
>> +unevaluatedProperties: false
>
> As mentioned elsewhere, not necessary here.
Yes, I withdraw this patch for the same reason.
Thank you,
---
Best Regards
Kunihiko Hayashi
prev parent reply other threads:[~2022-04-15 1:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 7:47 [PATCH] dt-bindings: interrrupt-controller: uniphier-aidet: Use unevaluatedProperties Kunihiko Hayashi
2022-04-13 19:09 ` Rob Herring
2022-04-15 1:17 ` Kunihiko Hayashi [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=2005f406-0117-b0eb-cc4b-2a921cf6528c@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mhiramat@kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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).