devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Alessandro Zummo <a.zummo@towertech.it>,
	linux-rtc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: rtc: ds1307: Convert to json-schema
Date: Thu, 21 Jul 2022 15:37:32 -0600	[thread overview]
Message-ID: <20220721213732.GA1993841-robh@kernel.org> (raw)
In-Reply-To: <20220617114420.1398259-1-thierry.reding@gmail.com>

On Fri, 17 Jun 2022 13:44:19 +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> Convert the DS1307 (and compatible) RTC bindings from the free-form text
> format to json-schema.
> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> Changes in v2:
> - add compatible string list for [ st,m41t00, dallas,ds1338 ]
> - allow second interrupt and interrupt-names
> - remove commented-out section
> - allow vcc-supply
> 
>  .../devicetree/bindings/rtc/rtc-ds1307.txt    |  52 ---------
>  .../devicetree/bindings/rtc/rtc-ds1307.yaml   | 102 ++++++++++++++++++
>  2 files changed, 102 insertions(+), 52 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/rtc/rtc-ds1307.txt
>  create mode 100644 Documentation/devicetree/bindings/rtc/rtc-ds1307.yaml
> 

Looks like this hasn't been picked up so I've applied both patches, 
thanks!

Rob


  parent reply	other threads:[~2022-07-21 21:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 11:44 [PATCH v2 1/2] dt-bindings: rtc: ds1307: Convert to json-schema Thierry Reding
2022-06-17 11:44 ` [PATCH v2 2/2] dt-bindings: rtc: Add EM Microelectronic EM3027 bindings Thierry Reding
2022-06-17 19:04   ` Rob Herring
2022-06-17 19:04 ` [PATCH v2 1/2] dt-bindings: rtc: ds1307: Convert to json-schema Rob Herring
2022-07-21 21:37 ` Rob Herring [this message]
2022-07-22 16:04   ` Alexandre Belloni
2022-08-04 18:03     ` 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=20220721213732.GA1993841-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@gmail.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 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).