Received: by 2002:a05:6602:18e:0:0:0:0 with SMTP id m14csp2055142ioo; Mon, 23 May 2022 09:07:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwI5ugaRpVQEpd1bs0a7sL1vUXbMbNfYCakS/9mAHHSfkAlWABNFfpUoz5+W+cfyFgKEzFr X-Received: by 2002:a05:6a00:140f:b0:4e0:6995:9c48 with SMTP id l15-20020a056a00140f00b004e069959c48mr24052283pfu.59.1653322032319; Mon, 23 May 2022 09:07:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1653322032; cv=none; d=google.com; s=arc-20160816; b=NBTiTiR2wXCTZ3g/urKM5mY7BiOHSO558mLzdnkvLWUd4FxEUkZ2Q9sDHNXZMSsvMb R/f1DqC+NcGNZs1srTHaEXrAJIo3fCHjB53FjPeLdri/ICV6s25HDLhw6/f2CRD9pwsU RiuvCLFOb8/ryOSrKmsmJs7/OatH0ej3ZGkMO7yxTeSQxX+vGjnWPmZ1Q8hMRsZjEbpH qOcP8gGBy4t7sz20BUHnGRw3RowqLWyuS1Dqb8dWnJO13Lh7/qevbZNcT0TXKT6MCvmw JQDK+O+l+SeAsVBc5eHuiLt9/BNb2/N4xzAJZI4EWzjB03jrkQvheACuELBShFJRNUFa CY/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=AGQoILiy4LEPWAMaB/P/KDVgjeEATtpXDhVmbmNdfHE=; b=Gge0GOLvy3vgEC64J5vAfP8+gUgsV6ZBqh7hDqxYN+HdUQwhVyoj2w0KKJG1VwneSw 9b6+b2DUme2Ih2ywAxaJyVUB5Q0P8mHy/bn9jU9en7oWAl9+BwaYUs01cZi8uxKngJK6 Utxuz0P+tsXXZ87FC2TubFr6uKdxKsrY0HNP5flyQVAVbekDZfjN7UhQOZc0dfJJgJMa dDwQ9iYCo1jy/KVEbnc9zJflGMSVb1pSnKiewCJhc6z05mk6wLN1MtoBMPcfq6+tyzX9 9+OlO3Nst4IR7Bo9L3BYhXwfbY3Es3RKLMfVcHcmycgC6HHx0pv0yTXkt21zy7yax7pU YWug== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=THwzKKHS; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id j10-20020a170902690a00b00153b2d16512si9572439plk.282.2022.05.23.09.07.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 23 May 2022 09:07:12 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=THwzKKHS; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 671DB12D36; Mon, 23 May 2022 09:06:05 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238361AbiEWQFm (ORCPT + 99 others); Mon, 23 May 2022 12:05:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59602 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236298AbiEWQFj (ORCPT ); Mon, 23 May 2022 12:05:39 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D1B2B62238; Mon, 23 May 2022 09:05:37 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 8597BB811A2; Mon, 23 May 2022 16:05:36 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 489ACC36AE3; Mon, 23 May 2022 16:05:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1653321935; bh=OQknoF9VpzvIZOY+XfmMknd+82/rB4Mw5f9LQzZr21Q=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=THwzKKHSSjXQ77sXx2/mcpyvFaPmuwRjPtkf+6ygcLIjgJnIBDkpbIoGiZwMJ+D5o T+Os+h+SfRSSB5mynrbHyKySYMlSc9gbVdbaFYm2rk3wjS+IFV9gUMNMjSv7IcPYcW anNXO9XUerx4AkqTQX0GuBwMZWJjJIt5SqG4Ryvu8vfzwx/oyUzm70pzl95EWk78lM 33y9fonnxN9UYmmowYJB8ebFwBbut1+jBF6rpsdduGTN4vnn5Ct04VIu3raTOiQUU5 zeVoBDObR5HIeoamYW7nQ6gjrZcQ1JfiGx7/YY/I1vKX8RMg0l/zT02dHb6ucB3tOi EuOU4h84/5hiA== Received: by mail-ej1-f42.google.com with SMTP id ck4so25538207ejb.8; Mon, 23 May 2022 09:05:35 -0700 (PDT) X-Gm-Message-State: AOAM531Vo4GYndTrQnp8GDI+ukiL9F9CYL9O1qP8lkLvvjPMiyI3U6gB G+AvvAcgoQq+ce42F5HCpXJBtf0jGAU59lv5bA== X-Received: by 2002:a17:907:3e8f:b0:6fe:d023:e147 with SMTP id hs15-20020a1709073e8f00b006fed023e147mr6512591ejc.270.1653321933416; Mon, 23 May 2022 09:05:33 -0700 (PDT) MIME-Version: 1.0 References: <20220512175011.28753-1-dipenp@nvidia.com> <20220518003508.GA1948162-robh@kernel.org> In-Reply-To: <20220518003508.GA1948162-robh@kernel.org> From: Rob Herring Date: Mon, 23 May 2022 11:05:21 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] dt-bindings: Renamed hte directory to timestamp To: Dipen Patel Cc: linux-tegra , devicetree@vger.kernel.org, Linus Walleij , "linux-kernel@vger.kernel.org" , Thierry Reding Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 17, 2022 at 7:35 PM Rob Herring 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 > > --- > > 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 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