linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: agross@kernel.org, devicetree@vger.kernel.org,
	ulf.hansson@linaro.org, linux-arm-msm@vger.kernel.org,
	bhupesh.linux@gmail.com, bjorn.andersson@linaro.org,
	linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mmc: sdhci-msm: Fix 'operating-points-v2 was unexpected' issue
Date: Tue, 9 Aug 2022 15:19:27 -0600	[thread overview]
Message-ID: <20220809211927.GA2419725-robh@kernel.org> (raw)
In-Reply-To: <20220725202709.2861789-1-bhupesh.sharma@linaro.org>

On Tue, 26 Jul 2022 01:57:09 +0530, Bhupesh Sharma wrote:
> As Rob reported in [1], there is one more issue present
> in the 'sdhci-msm' dt-binding which shows up when a fix for
> 'unevaluatedProperties' handling is applied:
> 
>  Documentation/devicetree/bindings/mmc/sdhci-msm.example.dtb:
>   mmc@8804000: Unevaluated properties are not allowed
>    ('operating-points-v2' was unexpected)
> 
> Fix the same.
> 
> [1]. https://lore.kernel.org/lkml/20220514220116.1008254-1-bhupesh.sharma@linaro.org/
> 
> Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Ulf Hansson <ulf.hansson@linaro.org>
> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
> ---
>  - Rebased on linux-next/master.
> 
>  Documentation/devicetree/bindings/mmc/sdhci-msm.yaml | 2 ++
>  1 file changed, 2 insertions(+)
> 

I picked this one up so it can be fixed for rc1.

Rob

      parent reply	other threads:[~2022-08-09 21:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 20:27 [PATCH] dt-bindings: mmc: sdhci-msm: Fix 'operating-points-v2 was unexpected' issue Bhupesh Sharma
2022-07-27 15:01 ` Rob Herring
2022-08-09 21:19 ` 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=20220809211927.GA2419725-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=agross@kernel.org \
    --cc=bhupesh.linux@gmail.com \
    --cc=bhupesh.sharma@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@linaro.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).