devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Dipen Patel <dipenp@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
	linus.walleij@linaro.org, devicetree@vger.kernel.org,
	robh+dt@kernel.org
Subject: Re: [PATCH] dt-bindings: timestamp: Correct id path
Date: Thu, 2 Jun 2022 17:57:34 +0200	[thread overview]
Message-ID: <Ypjd7lsn7KCDXBXv@orome> (raw)
In-Reply-To: <20220523172515.5941-1-dipenp@nvidia.com>

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

On Mon, May 23, 2022 at 10:25:15AM -0700, Dipen Patel wrote:
> During the repository renaming from hte to timestamp, $id path was not
> updated accordingly. This patch corrects $id path.
> 
> Fixes: af583852d2ef ("dt-bindings: Renamed hte directory to timestamp")
> Signed-off-by: Dipen Patel <dipenp@nvidia.com>
> ---
>  .../bindings/timestamp/hardware-timestamps-common.yaml          | 2 +-
>  Documentation/devicetree/bindings/timestamp/hte-consumer.yaml   | 2 +-
>  .../devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml      | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)

Sorry for the delay. I've applied this patch now and dt_binding_check
now no longer shows any errors for these files.

Thanks,
Thierry

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

      parent reply	other threads:[~2022-06-02 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 17:25 [PATCH] dt-bindings: timestamp: Correct id path Dipen Patel
2022-05-24  2:09 ` Rob Herring
2022-05-31 13:33 ` Rob Herring
2022-05-31 17:35   ` Dipen Patel
2022-05-31 21:42     ` Rob Herring
2022-05-31 22:53       ` Dipen Patel
2022-06-02 15:57 ` 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=Ypjd7lsn7KCDXBXv@orome \
    --to=thierry.reding@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dipenp@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh+dt@kernel.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 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).