From: Rob Herring <robh@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH] dt-bindings: spmi: Correct 'reg' schema
Date: Mon, 21 Jun 2021 11:03:11 -0600 [thread overview]
Message-ID: <20210621170311.GA975843@robh.at.kernel.org> (raw)
In-Reply-To: <20210615172024.856360-1-robh@kernel.org>
On Tue, 15 Jun 2021 11:20:24 -0600, Rob Herring wrote:
> 'reg' is defined to be N address entries of M cells each. For SPMI, N is 1
> and M is 1 or 2. The schema fails to define the number of entries as it
> only specifies the inner cell(s). To fix, add an outer items list with 1
> entry.
>
> Cc: Stephen Boyd <sboyd@kernel.org>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Documentation/devicetree/bindings/spmi/spmi.yaml | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2021-06-21 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 17:20 [PATCH] dt-bindings: spmi: Correct 'reg' schema Rob Herring
2021-06-21 17:03 ` Rob Herring [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=20210621170311.GA975843@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@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).