All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org,
	Alexandre Torgue <alexandre.torgue@st.com>,
	Arnaud Pouliquen <arnaud.pouliquen@st.com>,
	linux-kernel@vger.kernel.org,
	Fabien Dessenne <fabien.dessenne@st.com>,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] dt-bindings: remoteproc: convert stm32-rproc to json-schema
Date: Thu, 21 Nov 2019 08:58:15 -0600	[thread overview]
Message-ID: <20191121145815.GA4284@bogus> (raw)
In-Reply-To: <20191121095225.26775-1-arnaud.pouliquen@st.com>

On Thu, 21 Nov 2019 10:52:25 +0100, Arnaud Pouliquen wrote:
> Convert the STM32 remoteproc bindings to DT schema format using
> json-schema
> 
> Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
> ---
>  .../bindings/remoteproc/st,stm32-rproc.yaml   | 131 ++++++++++++++++++
>  .../bindings/remoteproc/stm32-rproc.txt       |  63 ---------
>  2 files changed, 131 insertions(+), 63 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/remoteproc/st,stm32-rproc.yaml
>  delete mode 100644 Documentation/devicetree/bindings/remoteproc/stm32-rproc.txt
> 

Applied, thanks.

Rob

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

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Alexandre Torgue <alexandre.torgue@st.com>,
	devicetree@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Fabien Dessenne <fabien.dessenne@st.com>,
	Arnaud Pouliquen <arnaud.pouliquen@st.com>
Subject: Re: [PATCH v2] dt-bindings: remoteproc: convert stm32-rproc to json-schema
Date: Thu, 21 Nov 2019 08:58:15 -0600	[thread overview]
Message-ID: <20191121145815.GA4284@bogus> (raw)
In-Reply-To: <20191121095225.26775-1-arnaud.pouliquen@st.com>

On Thu, 21 Nov 2019 10:52:25 +0100, Arnaud Pouliquen wrote:
> Convert the STM32 remoteproc bindings to DT schema format using
> json-schema
> 
> Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
> ---
>  .../bindings/remoteproc/st,stm32-rproc.yaml   | 131 ++++++++++++++++++
>  .../bindings/remoteproc/stm32-rproc.txt       |  63 ---------
>  2 files changed, 131 insertions(+), 63 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/remoteproc/st,stm32-rproc.yaml
>  delete mode 100644 Documentation/devicetree/bindings/remoteproc/stm32-rproc.txt
> 

Applied, thanks.

Rob

  reply	other threads:[~2019-11-21 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21  9:52 [PATCH v2] dt-bindings: remoteproc: convert stm32-rproc to json-schema Arnaud Pouliquen
2019-11-21  9:52 ` Arnaud Pouliquen
2019-11-21 14:58 ` Rob Herring [this message]
2019-11-21 14:58   ` 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=20191121145815.GA4284@bogus \
    --to=robh@kernel.org \
    --cc=alexandre.torgue@st.com \
    --cc=arnaud.pouliquen@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabien.dessenne@st.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mark.rutland@arm.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.