From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Rob Herring <robh@kernel.org>, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: nvmem: use base meta-schema for consumer schema
Date: Wed, 17 Mar 2021 08:54:43 +0000 [thread overview]
Message-ID: <b91daddf-6162-3679-ff7b-354170e0d0fb@linaro.org> (raw)
In-Reply-To: <20210316195111.3531755-1-robh@kernel.org>
On 16/03/2021 19:51, Rob Herring wrote:
> Common consumer schemas need to use the base.yaml meta-schema because
> they need to define different constraints (e.g. the type) from what
> users of the common schema need to define (e.g. how many entries).
>
> Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
Reviewed-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
--srini
> Documentation/devicetree/bindings/nvmem/nvmem-consumer.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/nvmem/nvmem-consumer.yaml b/Documentation/devicetree/bindings/nvmem/nvmem-consumer.yaml
> index 828e4a1ece41..b1da238c8bcb 100644
> --- a/Documentation/devicetree/bindings/nvmem/nvmem-consumer.yaml
> +++ b/Documentation/devicetree/bindings/nvmem/nvmem-consumer.yaml
> @@ -2,7 +2,7 @@
> %YAML 1.2
> ---
> $id: http://devicetree.org/schemas/nvmem/nvmem-consumer.yaml#
> -$schema: http://devicetree.org/meta-schemas/core.yaml#
> +$schema: http://devicetree.org/meta-schemas/base.yaml#
>
> title: NVMEM (Non Volatile Memory) Consumer Device Tree Bindings
>
>
prev parent reply other threads:[~2021-03-17 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 19:51 [PATCH] dt-bindings: nvmem: use base meta-schema for consumer schema Rob Herring
2021-03-17 8:54 ` Srinivas Kandagatla [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=b91daddf-6162-3679-ff7b-354170e0d0fb@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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).