From: Rob Herring <robh@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: linux-arm-kernel@lists.infradead.org,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Rob Herring <robh+dt@kernel.org>,
linux-stm32@st-md-mailman.stormreply.com,
devicetree@vger.kernel.org, Wolfram Sang <wsa@kernel.org>,
Alain Volmat <alain.volmat@foss.st.com>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: i2c: st,stm32-i2c: Document wakeup-source property
Date: Thu, 29 Sep 2022 16:56:05 -0500 [thread overview]
Message-ID: <166448856463.2774018.6148210751198203104.robh@kernel.org> (raw)
In-Reply-To: <20220926204653.381722-1-marex@denx.de>
On Mon, 26 Sep 2022 22:46:53 +0200, Marek Vasut wrote:
> Document wakeup-source property. This fixes dtbs_check warnings
> when building current Linux DTs:
>
> "
> arch/arm/boot/dts/stm32mp153c-dhcom-drc02.dtb: i2c@40015000: Unevaluated properties are not allowed ('wakeup-source' was unexpected)
> "
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
> Cc: Alain Volmat <alain.volmat@foss.st.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Wolfram Sang <wsa@kernel.org>
> Cc: devicetree@vger.kernel.org
> Cc: linux-i2c@vger.kernel.org
> Cc: linux-stm32@st-md-mailman.stormreply.com
> To: linux-arm-kernel@lists.infradead.org
> ---
> Documentation/devicetree/bindings/i2c/st,stm32-i2c.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-09-29 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 20:46 [PATCH] dt-bindings: i2c: st,stm32-i2c: Document wakeup-source property Marek Vasut
2022-09-29 21:56 ` Rob Herring [this message]
2022-10-01 22:35 ` Wolfram Sang
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=166448856463.2774018.6148210751198203104.robh@kernel.org \
--to=robh@kernel.org \
--cc=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marex@denx.de \
--cc=robh+dt@kernel.org \
--cc=wsa@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