Received: by 2002:a05:7412:b995:b0:f9:9502:5bb8 with SMTP id it21csp1058598rdb; Fri, 22 Dec 2023 13:19:53 -0800 (PST) X-Google-Smtp-Source: AGHT+IExCFeJZmJFFK4eCQmheYfMdZHDcKsppvcTilhZ47qIjDQdVR0jF6Wy15EUIdX5unPidqnw X-Received: by 2002:a05:6e02:12cd:b0:35d:962b:aea4 with SMTP id i13-20020a056e0212cd00b0035d962baea4mr2484143ilm.7.1703279993075; Fri, 22 Dec 2023 13:19:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1703279993; cv=none; d=google.com; s=arc-20160816; b=ftGV9v1Y2rrcf6o1/0eQP1LUKsDpoFFwN5URoYGBtPNZuPEXrJVEvzANfVgC/geFnV aMiuGHvCz7xJz7Y5N+TSo6yV4y/DGG7lt6mtGvPLzAcw9JFcgNjV0GEDk8Xi6Y2vufjJ KgQKGMezBwwM9iyo3u85l/c02yEc5RBtWTI/qtD9uEzX1oB0u+bCLdbunXS5l69cxOKm W32FFXOMFUnpIAgGF4t5qV7F/7KciF7e3tC/hZy+D+yDmY8KD+nR9WVOYhvAD0W4+ds6 hWm4k+83uPMqJaci4FOUeTXSLrk2zqaVjg6UyqP/dcEO+3OT8LxXC1UuqWgk58osAwwO qZQA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=date:subject:message-id:references:in-reply-to:cc:to:from :mime-version:list-unsubscribe:list-subscribe:list-id:precedence :content-transfer-encoding:dkim-signature; bh=z59ZA3nky5PCEVnhB4gy74GkN6n/vopsIVb5YPJCjtE=; fh=WacJiZN+vMq1ap3PDmg+3MzLVgeyJt4xvz1v5RygRH8=; b=dm+Rz/k+/xO+J+ohz5i/vxTNfvHSZgxUbHRgxay8ZoVSdKTs92F5XDnZSY0+IlgMaV Scbu2BThZlCWODXsuPalpPQx/XjUBxiPoIznELEzpRehwA/DEwSne7uX3esGIMxpQGWt FlO1AWCcdBJIZ/6ut4sMVFCJwKIrhU3n5jdyne+WKgHgBGF9YoIEIzrSGYD1fmKIiHRC kxWUtgcca24dprE6K7CAtCYPTzjSiOkXg5XhqiahJ8nI2lpZZ2saf6yXPt7n+QrjSjul bfwfeB4EAe3dgjpcUX/A5Nz+7DA9ddAVZRRqTlgtC7WBDP1Qg0x7WvYWmig7fiVhhyJa isDg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=XutJyryH; spf=pass (google.com: domain of linux-kernel+bounces-10066-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-10066-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [139.178.88.99]) by mx.google.com with ESMTPS id k2-20020a170902c40200b001d3fbe6900dsi3830760plk.622.2023.12.22.13.19.52 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Dec 2023 13:19:53 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-10066-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=XutJyryH; spf=pass (google.com: domain of linux-kernel+bounces-10066-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-10066-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 2A0C928621B for ; Fri, 22 Dec 2023 21:19:52 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id A78A02EAE2; Fri, 22 Dec 2023 21:19:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="XutJyryH" X-Original-To: linux-kernel@vger.kernel.org Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BED062E82A; Fri, 22 Dec 2023 21:19:43 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D8469C433C8; Fri, 22 Dec 2023 21:19:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1703279983; bh=85pem+bV3h4CTSEJsl8gxNpUqeC+ByEZF8tHZajdLdo=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=XutJyryH1C0yuKZA/mta5BFslea1nPHuuMEMIqTexQjedrgggkrdf3eqN2kD6EkgU 3jCx87FzTjHItInuySR3YJOOZmFV211W9WBPfOQXj+lHVaF9uXE6yR6kBTdYnjJhdQ s70fgyCI5FDyEx/7pzbczFpZNRK/qYjTXh+G6TNTSIAAXIHxfpWMzIAO4LYqjrX9U5 wAjkBSNhgkiJ/W8etslilyY1mQKWxdEWarTXXTaBT+uPKmD129ajAHNB4wLfI2NAKS isigYPWU3YdtSbDmSciHfVtXZ1A1wrIOZH52LLSxoazUgCso3tswSPt13z5HfEGnjQ qfE7JAi8wYz6Q== Received: (nullmailer pid 2942328 invoked by uid 1000); Fri, 22 Dec 2023 21:19:39 -0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 From: Rob Herring To: Alexander Graf Cc: Peter Zijlstra , Tom Lendacky , Usama Arif , Benjamin Herrenschmidt , David Woodhouse , Andrew Morton , madvenka@linux.microsoft.com, Ashish Kalra , Eric Biederman , linux-kernel@vger.kernel.org, "H. Peter Anvin" , kexec@lists.infradead.org, Steven Rostedt , pbonzini@redhat.com, Anthony Yznaga , arnd@arndb.de, linux-doc@vger.kernel.org, linux-mm@kvack.org, devicetree@vger.kernel.org, Mark Rutland , linux-trace-kernel@vger.kernel.org, Andy Lutomirski , Rob Herring , Stanislav Kinsburskii , James Gowans , x86@kernel.org, linux-arm-kernel@lists.infradead.org In-Reply-To: <20231222195144.24532-12-graf@amazon.com> References: <20231222193607.15474-1-graf@amazon.com> <20231222195144.24532-1-graf@amazon.com> <20231222195144.24532-12-graf@amazon.com> Message-Id: <170327997978.2942294.14458926896132199704.robh@kernel.org> Subject: Re: [PATCH v2 17/17] devicetree: Add bindings for ftrace KHO Date: Fri, 22 Dec 2023 15:19:39 -0600 On Fri, 22 Dec 2023 19:51:44 +0000, Alexander Graf wrote: > With ftrace in KHO, we are creating an ABI between old kernel and new > kernel about the state that they transfer. To ensure that we document > that state and catch any breaking change, let's add its schema to the > common devicetree bindings. This way, we can quickly reason about the > state that gets passed. > > Signed-off-by: Alexander Graf > --- > .../bindings/kho/ftrace/ftrace-array.yaml | 46 +++++++++++++++ > .../bindings/kho/ftrace/ftrace-cpu.yaml | 56 +++++++++++++++++++ > .../bindings/kho/ftrace/ftrace.yaml | 48 ++++++++++++++++ > 3 files changed, 150 insertions(+) > create mode 100644 Documentation/devicetree/bindings/kho/ftrace/ftrace-array.yaml > create mode 100644 Documentation/devicetree/bindings/kho/ftrace/ftrace-cpu.yaml > create mode 100644 Documentation/devicetree/bindings/kho/ftrace/ftrace.yaml > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' on your patch (DT_CHECKER_FLAGS is new in v5.13): yamllint warnings/errors: ./Documentation/devicetree/bindings/kho/ftrace/ftrace-array.yaml:43:111: [warning] line too long (117 > 110 characters) (line-length) ./Documentation/devicetree/bindings/kho/ftrace/ftrace-cpu.yaml:53:111: [warning] line too long (117 > 110 characters) (line-length) ./Documentation/devicetree/bindings/kho/ftrace/ftrace.yaml:45:111: [warning] line too long (117 > 110 characters) (line-length) dtschema/dtc warnings/errors: WARNING: Documentation/devicetree/bindings/kho/ftrace/ftrace-array.example.dts:29.25-39: Value 0x0000000101000000 truncated to 0x01000000 WARNING: Documentation/devicetree/bindings/kho/ftrace/ftrace-array.example.dts:29.48-62: Value 0x0000000101000100 truncated to 0x01000100 WARNING: Documentation/devicetree/bindings/kho/ftrace/ftrace-array.example.dts:29.73-87: Value 0x0000000101000038 truncated to 0x01000038 WARNING: Documentation/devicetree/bindings/kho/ftrace/ftrace-array.example.dts:29.96-110: Value 0x0000000101002000 truncated to 0x01002000 WARNING: Documentation/devicetree/bindings/kho/ftrace/ftrace-cpu.example.dts:29.25-39: Value 0x0000000101000000 truncated to 0x01000000 WARNING: Documentation/devicetree/bindings/kho/ftrace/ftrace-cpu.example.dts:29.48-62: Value 0x0000000101000100 truncated to 0x01000100 WARNING: Documentation/devicetree/bindings/kho/ftrace/ftrace-cpu.example.dts:29.73-87: Value 0x0000000101000038 truncated to 0x01000038 WARNING: Documentation/devicetree/bindings/kho/ftrace/ftrace-cpu.example.dts:29.96-110: Value 0x0000000101002000 truncated to 0x01002000 WARNING: Documentation/devicetree/bindings/kho/ftrace/ftrace.example.dts:29.25-39: Value 0x0000000101000000 truncated to 0x01000000 WARNING: Documentation/devicetree/bindings/kho/ftrace/ftrace.example.dts:29.48-62: Value 0x0000000101000100 truncated to 0x01000100 WARNING: Documentation/devicetree/bindings/kho/ftrace/ftrace.example.dts:29.73-87: Value 0x0000000101000038 truncated to 0x01000038 WARNING: Documentation/devicetree/bindings/kho/ftrace/ftrace.example.dts:29.96-110: Value 0x0000000101002000 truncated to 0x01002000 doc reference errors (make refcheckdocs): See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20231222195144.24532-12-graf@amazon.com The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch. If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date: pip3 install dtschema --upgrade Please check and re-submit after running the above command yourself. Note that DT_SCHEMA_FILES can be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.