All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Daniele Alessandrelli <daniele.alessandrelli@linux.intel.com>
Cc: Daniele Alessandrelli <daniele.alessandrelli@intel.com>,
	Mark Gross <mgross@linux.intel.com>,
	devicetree@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	Rob Herring <robh+dt@kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: Add Keem Bay OCS AES bindings
Date: Tue, 8 Dec 2020 10:15:19 -0600	[thread overview]
Message-ID: <20201208161519.GA2630335@robh.at.kernel.org> (raw)
In-Reply-To: <20201126115148.68039-2-daniele.alessandrelli@linux.intel.com>

On Thu, 26 Nov 2020 11:51:47 +0000, Daniele Alessandrelli wrote:
> From: Daniele Alessandrelli <daniele.alessandrelli@intel.com>
> 
> Add device-tree bindings for Intel Keem Bay Offload and Crypto Subsystem
> (OCS) AES crypto driver.
> 
> Signed-off-by: Daniele Alessandrelli <daniele.alessandrelli@intel.com>
> Acked-by: Mark Gross <mgross@linux.intel.com>
> ---
>  .../crypto/intel,keembay-ocs-aes.yaml         | 45 +++++++++++++++++++
>  1 file changed, 45 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/crypto/intel,keembay-ocs-aes.yaml
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2020-12-08 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 11:51 [PATCH 0/2] crypto: Add Keem Bay OCS AES/SM4 driver Daniele Alessandrelli
2020-11-26 11:51 ` [PATCH 1/2] dt-bindings: Add Keem Bay OCS AES bindings Daniele Alessandrelli
2020-12-08 16:15   ` Rob Herring [this message]
2020-11-26 11:51 ` [PATCH 2/2] crypto: keembay-ocs-aes: Add support for Keem Bay OCS AES/SM4 Daniele Alessandrelli
2020-12-11 10:13 ` [PATCH 0/2] crypto: Add Keem Bay OCS AES/SM4 driver Herbert Xu

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=20201208161519.GA2630335@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=daniele.alessandrelli@intel.com \
    --cc=daniele.alessandrelli@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=mgross@linux.intel.com \
    --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 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.