All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jon Hunter <jonathanh@nvidia.com>,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: timer: tegra: Convert to json-schema
Date: Thu, 6 Jul 2023 15:27:43 +0200	[thread overview]
Message-ID: <ZKbBTye-aaDOYpCy@orome> (raw)
In-Reply-To: <20230705204723.GA1866650-robh@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 968 bytes --]

On Wed, Jul 05, 2023 at 02:47:23PM -0600, Rob Herring wrote:
> On Wed, Jul 05, 2023 at 05:30:56PM +0200, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> > 
> > Convert the Tegra timer bindings from the free-form text format to
> > json-schema.
> > 
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> >  .../bindings/timer/nvidia,tegra20-timer.yaml  | 121 ++++++++++++++++++
> >  .../bindings/timer/nvidia,tegra210-timer.yaml |  70 ++++++++++
> >  2 files changed, 191 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/timer/nvidia,tegra20-timer.yaml
> >  create mode 100644 Documentation/devicetree/bindings/timer/nvidia,tegra210-timer.yaml
> 
> Convert? Where's the removal?

Ugh... nevermind. Somebody beat me to it and I hadn't noticed that the
plain text files had rebased out. These were merged into a combined DT
binding in nvidia,tegra-timer.yaml.

Sorry for the noise.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-07-06 13:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 15:30 [PATCH] dt-bindings: timer: tegra: Convert to json-schema Thierry Reding
2023-07-05 20:47 ` Rob Herring
2023-07-06 13:27   ` Thierry Reding [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=ZKbBTye-aaDOYpCy@orome \
    --to=thierry.reding@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tglx@linutronix.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 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.