From: Rob Herring <robh@kernel.org>
To: Tudor Ambarus <tudor.ambarus@microchip.com>
Cc: linux-kernel@vger.kernel.org, krzysztof.kozlowski@canonical.com,
kavyasree.kotagiri@microchip.com, herbert@gondor.apana.org.au,
alexandre.belloni@bootlin.com, devicetree@vger.kernel.org,
claudiu.beznea@microchip.com, linux-crypto@vger.kernel.org,
nicolas.ferre@microchip.com, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PACTH v4 1/3] dt-bindings: crypto: Convert Atmel AES to yaml
Date: Thu, 17 Feb 2022 17:28:33 -0600 [thread overview]
Message-ID: <Yg7aIXP2QjOiFlIK@robh.at.kernel.org> (raw)
In-Reply-To: <20220211093922.456634-2-tudor.ambarus@microchip.com>
On Fri, 11 Feb 2022 11:39:20 +0200, Tudor Ambarus wrote:
> Convert Atmel AES documentation to yaml format. With the conversion the
> clock and clock-names properties are made mandatory. The driver returns
> -EINVAL if "aes_clk" is not found, reflect that in the bindings and make
> the clock and clock-names properties mandatory. Update the example to
> better describe how one should define the dt node.
>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> ---
> .../crypto/atmel,at91sam9g46-aes.yaml | 66 +++++++++++++++++++
> .../bindings/crypto/atmel-crypto.txt | 20 ------
> 2 files changed, 66 insertions(+), 20 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-aes.yaml
>
Applied, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Tudor Ambarus <tudor.ambarus@microchip.com>
Cc: devicetree@vger.kernel.org, alexandre.belloni@bootlin.com,
herbert@gondor.apana.org.au, krzysztof.kozlowski@canonical.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
linux-crypto@vger.kernel.org, kavyasree.kotagiri@microchip.com,
claudiu.beznea@microchip.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PACTH v4 1/3] dt-bindings: crypto: Convert Atmel AES to yaml
Date: Thu, 17 Feb 2022 17:28:33 -0600 [thread overview]
Message-ID: <Yg7aIXP2QjOiFlIK@robh.at.kernel.org> (raw)
In-Reply-To: <20220211093922.456634-2-tudor.ambarus@microchip.com>
On Fri, 11 Feb 2022 11:39:20 +0200, Tudor Ambarus wrote:
> Convert Atmel AES documentation to yaml format. With the conversion the
> clock and clock-names properties are made mandatory. The driver returns
> -EINVAL if "aes_clk" is not found, reflect that in the bindings and make
> the clock and clock-names properties mandatory. Update the example to
> better describe how one should define the dt node.
>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> ---
> .../crypto/atmel,at91sam9g46-aes.yaml | 66 +++++++++++++++++++
> .../bindings/crypto/atmel-crypto.txt | 20 ------
> 2 files changed, 66 insertions(+), 20 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-aes.yaml
>
Applied, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-17 23:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 9:39 [PACTH v4 0/3] dt-bindings: crypto: Convert atmel-crypto to YAML Tudor Ambarus
2022-02-11 9:39 ` Tudor Ambarus
2022-02-11 9:39 ` [PACTH v4 1/3] dt-bindings: crypto: Convert Atmel AES to yaml Tudor Ambarus
2022-02-11 9:39 ` Tudor Ambarus
2022-02-17 23:28 ` Rob Herring [this message]
2022-02-17 23:28 ` Rob Herring
2022-02-11 9:39 ` [PACTH v4 2/3] dt-bindings: crypto: Convert Atmel TDES " Tudor Ambarus
2022-02-11 9:39 ` Tudor Ambarus
2022-02-17 23:28 ` Rob Herring
2022-02-17 23:28 ` Rob Herring
2022-02-11 9:39 ` [PACTH v4 3/3] dt-bindings: crypto: Convert Atmel SHA " Tudor Ambarus
2022-02-11 9:39 ` Tudor Ambarus
2022-02-17 23:29 ` Rob Herring
2022-02-17 23:29 ` Rob Herring
2022-02-11 10:14 ` [PACTH v4 0/3] dt-bindings: crypto: Convert atmel-crypto to YAML Claudiu.Beznea
2022-02-11 10:14 ` Claudiu.Beznea
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=Yg7aIXP2QjOiFlIK@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kavyasree.kotagiri@microchip.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=tudor.ambarus@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.