From: Rob Herring <robh@kernel.org>
To: Daniele Alessandrelli <daniele.alessandrelli@linux.intel.com>
Cc: linux-crypto@vger.kernel.org,
Daniele Alessandrelli <daniele.alessandrelli@intel.com>,
Declan Murphy <declan.murphy@intel.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Mark Gross <mgross@linux.intel.com>,
devicetree@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v3 1/3] dt-bindings: crypto: Add Keem Bay OCS HCU bindings
Date: Tue, 1 Dec 2020 12:39:15 -0700 [thread overview]
Message-ID: <20201201193915.GA930982@robh.at.kernel.org> (raw)
In-Reply-To: <20201116185846.773464-2-daniele.alessandrelli@linux.intel.com>
On Mon, 16 Nov 2020 18:58:44 +0000, Daniele Alessandrelli wrote:
> From: Declan Murphy <declan.murphy@intel.com>
>
> Add device-tree bindings for the Intel Keem Bay Offload Crypto Subsystem
> (OCS) Hashing Control Unit (HCU) crypto driver.
>
> Signed-off-by: Declan Murphy <declan.murphy@intel.com>
> Signed-off-by: Daniele Alessandrelli <daniele.alessandrelli@intel.com>
> Acked-by: Mark Gross <mgross@linux.intel.com>
> ---
> .../crypto/intel,keembay-ocs-hcu.yaml | 46 +++++++++++++++++++
> 1 file changed, 46 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/crypto/intel,keembay-ocs-hcu.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-12-01 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 18:58 [PATCH v3 0/3] crypto: Add Keem Bay OCS HCU driver Daniele Alessandrelli
2020-11-16 18:58 ` [PATCH v3 1/3] dt-bindings: crypto: Add Keem Bay OCS HCU bindings Daniele Alessandrelli
2020-12-01 19:39 ` Rob Herring [this message]
2020-11-16 18:58 ` [PATCH v3 2/3] crypto: keembay: Add Keem Bay OCS HCU driver Daniele Alessandrelli
2020-11-19 23:15 ` mark gross
2020-12-14 19:11 ` Daniele Alessandrelli
2020-11-16 18:58 ` [PATCH v3 3/3] MAINTAINERS: Add maintainers for " Daniele Alessandrelli
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=20201201193915.GA930982@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=daniele.alessandrelli@intel.com \
--cc=daniele.alessandrelli@linux.intel.com \
--cc=davem@davemloft.net \
--cc=declan.murphy@intel.com \
--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 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).