From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Varshini.Rajendran@microchip.com, herbert@gondor.apana.org.au,
davem@davemloft.net, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
Nicolas.Ferre@microchip.com, alexandre.belloni@bootlin.com,
claudiu.beznea@microchip.com, linux-crypto@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 11/50] dt-bindings: crypto: add sam9x7 in Atmel TDES
Date: Thu, 10 Aug 2023 08:22:13 +0100 [thread overview]
Message-ID: <37782447-43c7-50f9-b9b4-5fbca94ce8c6@linaro.org> (raw)
In-Reply-To: <1ec901d0-44c2-1d28-5976-d93abfffee67@microchip.com>
On 8/10/23 06:38, Varshini.Rajendran@microchip.com wrote:
>> On 7/28/23 11:24, Varshini Rajendran wrote:
>>> Add DT bindings for atmel TDES.
>> NACK. The atmel crypto drivers check the version at runtime and
>> fill a capabilities structure based on the version identified.
>> There's a single compatible regardless of the version of the IP
>> used until now, why do you want to change it?
>>
> Hi Tudor,
Hi,
>
> I am aware that there is no change in the crypto IP used. This patch is
> to add a SoC specific compatible as expected by writing-bindings
> guideline. Maybe a bit more explanation in the commit description might
> do the trick.
>
So you add a compatible that will never be used just to comply with
the writing bindings guideline?
next prev parent reply other threads:[~2023-08-10 7:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 10:24 [PATCH v3 11/50] dt-bindings: crypto: add sam9x7 in Atmel TDES Varshini Rajendran
2023-07-28 11:17 ` Tudor Ambarus
2023-08-10 5:38 ` Varshini.Rajendran
2023-08-10 7:22 ` Tudor Ambarus [this message]
2023-08-19 14:34 ` Krzysztof Kozlowski
2023-08-21 8:41 ` Nicolas Ferre
2023-08-21 9:54 ` Tudor Ambarus
2023-08-21 12:10 ` Krzysztof Kozlowski
2023-08-21 13:00 ` Tudor Ambarus
2023-08-21 13:12 ` Krzysztof Kozlowski
2023-08-21 8:59 ` Nicolas Ferre
2023-08-21 9:59 ` Tudor Ambarus
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=37782447-43c7-50f9-b9b4-5fbca94ce8c6@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=Nicolas.Ferre@microchip.com \
--cc=Varshini.Rajendran@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).