From: Rob Herring <robh@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@st.com>
Cc: wim@linux-watchdog.org, linux@roeck-us.net, mark.rutland@arm.com,
alexandre.torgue@st.com, linux-watchdog@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: watchdog: Convert stm32 watchdog bindings to json-schema
Date: Thu, 19 Dec 2019 09:51:02 -0600 [thread overview]
Message-ID: <20191219155102.GA26498@bogus> (raw)
In-Reply-To: <20191121084316.13839-1-benjamin.gaignard@st.com>
On Thu, Nov 21, 2019 at 09:43:16AM +0100, Benjamin Gaignard wrote:
> Convert the STM32 watchdog binding to DT schema format using json-schema
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> changes in version 2:
> - remove trailer space
> - add Christophe in the maintainers list
>
> .../devicetree/bindings/watchdog/st,stm32-iwdg.txt | 26 ----------
> .../bindings/watchdog/st,stm32-iwdg.yaml | 55 ++++++++++++++++++++++
> 2 files changed, 55 insertions(+), 26 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/watchdog/st,stm32-iwdg.txt
> create mode 100644 Documentation/devicetree/bindings/watchdog/st,stm32-iwdg.yaml
Fixed up a typo with 'enums' and applied.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@st.com>
Cc: mark.rutland@arm.com, alexandre.torgue@st.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, wim@linux-watchdog.org,
linux-stm32@st-md-mailman.stormreply.com, linux@roeck-us.net,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: watchdog: Convert stm32 watchdog bindings to json-schema
Date: Thu, 19 Dec 2019 09:51:02 -0600 [thread overview]
Message-ID: <20191219155102.GA26498@bogus> (raw)
In-Reply-To: <20191121084316.13839-1-benjamin.gaignard@st.com>
On Thu, Nov 21, 2019 at 09:43:16AM +0100, Benjamin Gaignard wrote:
> Convert the STM32 watchdog binding to DT schema format using json-schema
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> changes in version 2:
> - remove trailer space
> - add Christophe in the maintainers list
>
> .../devicetree/bindings/watchdog/st,stm32-iwdg.txt | 26 ----------
> .../bindings/watchdog/st,stm32-iwdg.yaml | 55 ++++++++++++++++++++++
> 2 files changed, 55 insertions(+), 26 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/watchdog/st,stm32-iwdg.txt
> create mode 100644 Documentation/devicetree/bindings/watchdog/st,stm32-iwdg.yaml
Fixed up a typo with 'enums' and applied.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-19 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 8:43 [PATCH v2] dt-bindings: watchdog: Convert stm32 watchdog bindings to json-schema Benjamin Gaignard
2019-11-21 8:43 ` Benjamin Gaignard
2019-12-19 15:51 ` Rob Herring [this message]
2019-12-19 15:51 ` 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=20191219155102.GA26498@bogus \
--to=robh@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=wim@linux-watchdog.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 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.