From: Rob Herring <robh@kernel.org>
To: Apurva Nandan <a-nandan@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, Nishanth Menon <nm@ti.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
devicetree@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Santosh Shilimkar <ssantosh@kernel.org>,
Tero Kristo <kristo@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Marc Zyngier <maz@kernel.org>,
linux-mmc@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, Hari Nagalla <hnagalla@ti.com>
Subject: Re: [PATCH 2/3] dt-bindings: mmc: Fix 'dma-coherent' was unexpected
Date: Mon, 22 Aug 2022 14:16:26 -0500 [thread overview]
Message-ID: <20220822191626.GA260589-robh@kernel.org> (raw)
In-Reply-To: <20220819190729.32358-3-a-nandan@ti.com>
On Sat, 20 Aug 2022 00:37:28 +0530, Apurva Nandan wrote:
> dma-coherent is mentioned in almost all TI K3 platform mmc
> nodes. Fix warning generated due to its missing match in
> yaml schema.
>
> Signed-off-by: Apurva Nandan <a-nandan@ti.com>
> ---
> Documentation/devicetree/bindings/mmc/sdhci-am654.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-08-22 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 19:07 [PATCH 0/3] Fix ti,sci-inta/intr and mmc dtbs_check warnings for TI K3 platforms Apurva Nandan
2022-08-19 19:07 ` [PATCH 1/3] dt-bindings: irqchip: ti,sci-inta: Fix warning '#interrupt-cells' was unexpected Apurva Nandan
2022-08-22 19:14 ` Rob Herring
2022-08-19 19:07 ` [PATCH 2/3] dt-bindings: mmc: Fix 'dma-coherent' " Apurva Nandan
2022-08-22 19:16 ` Rob Herring [this message]
2022-08-26 9:16 ` Ulf Hansson
2022-08-19 19:07 ` [PATCH 3/3] dt-bindings: interrupt-controller: Fix 'reg' " Apurva Nandan
2022-08-22 19:16 ` Rob Herring
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=20220822191626.GA260589-robh@kernel.org \
--to=robh@kernel.org \
--cc=a-nandan@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=maz@kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=tglx@linutronix.de \
--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).