linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Rob Herring <robh@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	~okias/devicetree@lists.sr.ht, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] dt-bindings: misc: fastrpc convert bindings to yaml
Date: Tue, 18 Jan 2022 16:01:42 +0100	[thread overview]
Message-ID: <U2VW5R.K2NKZT1MORH03@ixit.cz> (raw)
In-Reply-To: <7A333484-F1D4-4D0E-97D5-6A40DEC44BFE@ixit.cz>

Should I pick different approach or keeping additionalProperties: true 
is suitable solution in this situation?

Thanks
David Heidelberg

On Sun, Dec 12 2021 at 13:03:40 +0000, David Heidelberg <david@ixit.cz> 
wrote:
> Well, since this is a subnode, some nodes are not converted yet and 
> at least know it'll bash about iommus, qcom,glink-channels and 
> qcom,smd-channels. I can change it to false, bit it'll print these 
> additional warnings, until other binding don't get converted.
> 
> David
> 
> 
>>  +    required:
>>  +      - compatible
>>  +      - reg
>>  +
>>  +    additionalProperties: true
> 
> Why? What other properties are present.
> 
>>  +
>>  +required:
>>  +  - compatible
>>  +  - label
>>  +  - '#address-cells'
>>  +  - '#size-cells'
>>  +
>>  +additionalProperties: true
> 
> Why? What other properties are present. This is generally never 
> correct.
> 
> Rob
> 



      reply	other threads:[~2022-01-18 15:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 10:15 [PATCH v4] dt-bindings: misc: fastrpc convert bindings to yaml David Heidelberg
2021-12-10 21:35 ` Rob Herring
2021-12-12 13:03   ` David Heidelberg
2022-01-18 15:01     ` David Heidelberg [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=U2VW5R.K2NKZT1MORH03@ixit.cz \
    --to=david@ixit.cz \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=~okias/devicetree@lists.sr.ht \
    /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).