From: Michal Simek <michal.simek@xilinx.com>
To: Herbert Xu <herbert@gondor.apana.org.au>, monstr@monstr.eu
Cc: Kalyani Akula <kalyania@xilinx.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
git <git@xilinx.com>, Harsh Jain <harshj@xilinx.com>,
Sarat Chand Savitala <saratcha@xilinx.com>,
Mohan Marutirao Dhanawade <mohand@xilinx.com>
Subject: Re: [PATCH V4 0/4] Add Xilinx's ZynqMP AES-GCM driver support
Date: Wed, 22 Jan 2020 07:59:48 +0100 [thread overview]
Message-ID: <7de607d1-e41a-724b-7fd6-714b5dda9384@xilinx.com> (raw)
In-Reply-To: <20200122055111.azr7zzhredywyusx@gondor.apana.org.au>
On 22. 01. 20 6:51, Herbert Xu wrote:
> On Tue, Jan 21, 2020 at 10:26:07AM +0100, Michal Simek wrote:
>>
>> All these drivers which requires firmware interface extension can be
>> added via your tree or I can take them via arm-soc tree with your ack.
>>
>> It is really up to you. I am happy to just ack patches out of crypto and
>> feel free to take them via your tree.
>> Or please let me know when you are done with review and I will take them.
>
> Thanks Michal. If you could ack them once they've been resubmitted
> then I can just take them via the cryptodev tree.
Great.
Michal
prev parent reply other threads:[~2020-01-22 7:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 7:43 Kalyani Akula
2019-11-20 7:43 ` [PATCH V4 1/4] dt-bindings: crypto: Add bindings for ZynqMP AES driver Kalyani Akula
2020-01-21 9:11 ` Michal Simek
2019-11-20 7:44 ` [PATCH V4 2/4] ARM64: zynqmp: Add Xilinix AES node Kalyani Akula
2020-01-21 9:13 ` Michal Simek
2019-11-20 7:44 ` [PATCH V4 3/4] firmware: xilinx: Add ZynqMP aes API for AES functionality Kalyani Akula
2020-01-21 9:15 ` Michal Simek
2019-11-20 7:44 ` [PATCH V4 4/4] crypto: Add Xilinx AES driver Kalyani Akula
2020-01-21 9:23 ` Michal Simek
2020-01-20 6:59 ` [PATCH V4 0/4] Add Xilinx's ZynqMP AES-GCM driver support Kalyani Akula
2020-01-20 7:55 ` Herbert Xu
2020-01-21 9:26 ` Michal Simek
2020-01-22 5:51 ` Herbert Xu
2020-01-22 6:59 ` Michal Simek [this message]
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=7de607d1-e41a-724b-7fd6-714b5dda9384@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=git@xilinx.com \
--cc=harshj@xilinx.com \
--cc=herbert@gondor.apana.org.au \
--cc=kalyania@xilinx.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mohand@xilinx.com \
--cc=monstr@monstr.eu \
--cc=saratcha@xilinx.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
all inboxes | Powered by JetHome®