mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dipen Patel <dipenp@nvidia.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: linux-tegra <linux-tegra@vger.kernel.org>,
	devicetree@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH] dt-bindings: Renamed hte directory to timestamp
Date: Mon, 23 May 2022 10:26:39 -0700	[thread overview]
Message-ID: <c7abec4b-69c1-d075-bb22-931a162694cc@nvidia.com> (raw)
In-Reply-To: <CAL_JsqK8hKVWChDNdmH7pB4kj2RafmEN0jFZSfi+i37uAPXhZw@mail.gmail.com>

Hi Rob,

I have just sent out the patch to fix this.

Best Regards,

Dipen Patel

On 5/23/22 9:05 AM, Rob Herring wrote:
> On Tue, May 17, 2022 at 7:35 PM Rob Herring <robh@kernel.org> wrote:
>> 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>
> I take that back:
>
> ./Documentation/devicetree/bindings/timestamp/hte-consumer.yaml: $id:
> relative path/filename doesn't match actual path or filename
> expected: http://devicetree.org/schemas/timestamp/hte-consumer.yaml#
> ./Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml:
> $id: relative path/filename doesn't match actual path or filename
> expected: http://devicetree.org/schemas/timestamp/nvidia,tegra194-hte.yaml#
> ./Documentation/devicetree/bindings/timestamp/hardware-timestamps-common.yaml:
> $id: relative path/filename doesn't match actual path or filename
> expected: http://devicetree.org/schemas/timestamp/hardware-timestamps-common.yaml#
>
>
> I was wondering why a new common binding was already in next without a
> Reviewed-by, but I let that slide. Now I regret doing that.
>
> Rob

      reply	other threads:[~2022-05-23 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 17:50 Dipen Patel
2022-05-13 20:53 ` Linus Walleij
2022-05-18  0:35 ` Rob Herring
2022-05-23 16:05   ` Rob Herring
2022-05-23 17:26     ` Dipen Patel [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=c7abec4b-69c1-d075-bb22-931a162694cc@nvidia.com \
    --to=dipenp@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --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

Powered by JetHome