All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Pierre-Yves MORDRET <pierre-yves.mordret@foss.st.com>,
	devicetree@vger.kernel.org,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	linux-i2c@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Alexandre Torgue <alexandre.torgue@foss.st.com>
Subject: Re: [PATCH] dt-bindings: i2c: stm32-i2c: Move st,syscfg-fmp definition to top level
Date: Sun, 23 Jan 2022 09:29:03 -0600	[thread overview]
Message-ID: <Ye10P+FlVPzsB7jR@robh.at.kernel.org> (raw)
In-Reply-To: <20220119174407.3810088-1-robh@kernel.org>

On Wed, 19 Jan 2022 11:44:07 -0600, Rob Herring wrote:
> It is preferred to define all properties in the main schema and leave
> if/then/else schemas to just be further constraints on properties.
> 
> Rework the schema to use be more specific for each cell. Previously,
> multiple entries of 3 cells each was allowed.
> 
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
>  .../devicetree/bindings/i2c/st,stm32-i2c.yaml | 24 ++++++++++---------
>  1 file changed, 13 insertions(+), 11 deletions(-)
> 

Applied, thanks!

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Pierre-Yves MORDRET <pierre-yves.mordret@foss.st.com>,
	devicetree@vger.kernel.org,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	linux-i2c@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Alexandre Torgue <alexandre.torgue@foss.st.com>
Subject: Re: [PATCH] dt-bindings: i2c: stm32-i2c: Move st,syscfg-fmp definition to top level
Date: Sun, 23 Jan 2022 09:29:03 -0600	[thread overview]
Message-ID: <Ye10P+FlVPzsB7jR@robh.at.kernel.org> (raw)
In-Reply-To: <20220119174407.3810088-1-robh@kernel.org>

On Wed, 19 Jan 2022 11:44:07 -0600, Rob Herring wrote:
> It is preferred to define all properties in the main schema and leave
> if/then/else schemas to just be further constraints on properties.
> 
> Rework the schema to use be more specific for each cell. Previously,
> multiple entries of 3 cells each was allowed.
> 
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
>  .../devicetree/bindings/i2c/st,stm32-i2c.yaml | 24 ++++++++++---------
>  1 file changed, 13 insertions(+), 11 deletions(-)
> 

Applied, thanks!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-01-23 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 17:44 [PATCH] dt-bindings: i2c: stm32-i2c: Move st,syscfg-fmp definition to top level Rob Herring
2022-01-19 17:44 ` [PATCH] dt-bindings: i2c: stm32-i2c: Move st, syscfg-fmp " Rob Herring
2022-01-23 15:29 ` Rob Herring [this message]
2022-01-23 15:29   ` [PATCH] dt-bindings: i2c: stm32-i2c: Move st,syscfg-fmp " 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=Ye10P+FlVPzsB7jR@robh.at.kernel.org \
    --to=robh@kernel.org \
    --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-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=pierre-yves.mordret@foss.st.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.