From: Rob Herring <robh@kernel.org>
To: Alain Volmat <alain.volmat@st.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
alexandre.torgue@st.com, wsa@the-dreams.de,
linux-kernel@vger.kernel.org, pierre-yves.mordret@st.com,
robh+dt@kernel.org, linux-i2c@vger.kernel.org,
mcoquelin.stm32@gmail.com, fabrice.gasnier@st.com,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] dt-bindings: i2c: stm32: Migrate i2c-stm32 documentation to yaml
Date: Thu, 21 Nov 2019 13:39:29 -0600 [thread overview]
Message-ID: <20191121193929.GA6676@bogus> (raw)
In-Reply-To: <1574342866-8348-1-git-send-email-alain.volmat@st.com>
On Thu, 21 Nov 2019 14:27:46 +0100, Alain Volmat wrote:
> The document was migrated to Yaml format and renamed st,stm32-i2c.yaml
>
> Signed-off-by: Alain Volmat <alain.volmat@st.com>
> ---
> v2: remove i2c-scl.*time description, ref (moved into i2c-controller.yaml
> push the st,syscfg-fmt into the if compatible st,stm32f7 part
> fix the st,syscfg-fmt ref syntax and set minItems/maxItems to 3
> make the clock-frequency part common and only keep enum in the st,stm32f4 case
> remove unnecesary minItems/maxItems
> remove address-cells/size-cells from required fields
> ---
> .../devicetree/bindings/i2c/i2c-stm32.txt | 65 ----------
> .../devicetree/bindings/i2c/st,stm32-i2c.yaml | 141 +++++++++++++++++++++
> 2 files changed, 141 insertions(+), 65 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/i2c/i2c-stm32.txt
> create mode 100644 Documentation/devicetree/bindings/i2c/st,stm32-i2c.yaml
>
Applied, thanks.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-11-21 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 13:27 [PATCH v2] dt-bindings: i2c: stm32: Migrate i2c-stm32 documentation to yaml Alain Volmat
2019-11-21 19:39 ` 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=20191121193929.GA6676@bogus \
--to=robh@kernel.org \
--cc=alain.volmat@st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=pierre-yves.mordret@st.com \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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).