public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: T Pratham <t-pratham@ti.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Praneeth Bajjuri <praneeth@ti.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Manorit Chawdhry <m-chawdhry@ti.com>,
	<devicetree@vger.kernel.org>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Conor Dooley <conor+dt@kernel.org>,
	Kamlesh Gurudasani <kamlesh@ti.com>,
	<linux-crypto@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v4 1/2] dt-bindings: crypto: Add binding for TI DTHE V2
Date: Tue, 3 Jun 2025 16:22:12 +0530	[thread overview]
Message-ID: <b254325e-32c6-4b5d-a20c-abe2888fea27@ti.com> (raw)
In-Reply-To: <174670267292.3889463.9488828665934209667.robh@kernel.org>

On 08/05/25 16:41, Rob Herring (Arm) wrote:
> 
> On Thu, 08 May 2025 15:37:40 +0530, T Pratham wrote:
>> Add DT binding for Texas Instruments DTHE V2 crypto accelerator.
>>
>> DTHE V2 is introduced as a part of TI AM62L SoC and can currently be
>> only found in it.
>>
>> Signed-off-by: T Pratham <t-pratham@ti.com>
>> ---
>>  .../bindings/crypto/ti,am62l-dthev2.yaml      | 50 +++++++++++++++++++
>>  MAINTAINERS                                   |  6 +++
>>  2 files changed, 56 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/crypto/ti,am62l-dthev2.yaml
>>
> 
> My bot found errors running 'make dt_binding_check' on your patch:
> 
> yamllint warnings/errors:
> 
> dtschema/dtc warnings/errors:
> 
> 
> doc reference errors (make refcheckdocs):
> 
> See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20250508101723.846210-3-t-pratham@ti.com
> 
Hi, the error logs here are empty. What does this mean (error, no error)?

Also, I ran `make dt_binding_check` locally and did not see any errors. Below dependencies are installed and up to date. 
> 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.
> 

Regards
T Pratham <t-pratham@ti.com>

  reply	other threads:[~2025-06-03 10:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 10:07 [PATCH v4 0/2] Add support for Texas Instruments DTHE V2 crypto accelerator T Pratham
2025-05-08 10:07 ` [PATCH v4 1/2] dt-bindings: crypto: Add binding for TI DTHE V2 T Pratham
2025-05-08 10:23   ` Krzysztof Kozlowski
2025-05-08 11:11   ` Rob Herring (Arm)
2025-06-03 10:52     ` T Pratham [this message]
2025-06-03 12:25       ` Krzysztof Kozlowski

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=b254325e-32c6-4b5d-a20c-abe2888fea27@ti.com \
    --to=t-pratham@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kamlesh@ti.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-chawdhry@ti.com \
    --cc=praneeth@ti.com \
    --cc=robh@kernel.org \
    --cc=vigneshr@ti.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