From: Rob Herring <robh@kernel.org>
To: Dipen Patel <dipenp@nvidia.com>
Cc: linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linus.walleij@linaro.org, linux-kernel@vger.kernel.org,
thierry.reding@gmail.com, robh+dt@kernel.org
Subject: Re: [PATCH] dt-bindings: Renamed hte directory to timestamp
Date: Tue, 17 May 2022 19:35:08 -0500 [thread overview]
Message-ID: <20220518003508.GA1948162-robh@kernel.org> (raw)
In-Reply-To: <20220512175011.28753-1-dipenp@nvidia.com>
On Thu, 12 May 2022 10:50:11 -0700, Dipen Patel wrote:
> Renamed hte dt binding directory to timestamp according review comment.
> Addressed minor comment about having HTE acronym first in the common dt
> binding document.
>
> The change reflects above renaming in MAINTAINERS files too.
>
> Signed-off-by: Dipen Patel <dipenp@nvidia.com>
> ---
> This patch is on top of old series (Intro to Hardware timestamping
> engine V6) present in linux-next tentatively in preparation for
> merge.
>
> .../{hte => timestamp}/hardware-timestamps-common.yaml | 6 +++---
> .../bindings/{hte => timestamp}/hte-consumer.yaml | 0
> .../bindings/{hte => timestamp}/nvidia,tegra194-hte.yaml | 0
> MAINTAINERS | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
> rename Documentation/devicetree/bindings/{hte => timestamp}/hardware-timestamps-common.yaml (71%)
> rename Documentation/devicetree/bindings/{hte => timestamp}/hte-consumer.yaml (100%)
> rename Documentation/devicetree/bindings/{hte => timestamp}/nvidia,tegra194-hte.yaml (100%)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-05-18 0:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 17:50 [PATCH] dt-bindings: Renamed hte directory to timestamp Dipen Patel
2022-05-13 20:53 ` Linus Walleij
2022-05-18 0:35 ` Rob Herring [this message]
2022-05-23 16:05 ` Rob Herring
2022-05-23 17:26 ` Dipen Patel
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=20220518003508.GA1948162-robh@kernel.org \
--to=robh@kernel.org \
--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 \
--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).