From: Chris Spencer <spencercw@gmail.com>
To: Horia Geanta <horia.geanta@nxp.com>
Cc: Aymen Sghaier <aymen.sghaier@nxp.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
Chris Spencer <christopher.spencer@sea.co.uk>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [RFC 0/4] crypto: caam - Add i.MX8MQ support
Date: Mon, 25 Feb 2019 14:17:03 +0000 [thread overview]
Message-ID: <CAGUNXRTe_G91TN-3qP-TAACB6kLXgJn-on5VGCJWbMqrv+rBWw@mail.gmail.com> (raw)
In-Reply-To: <VI1PR0402MB348578FE91831D11CDCC91D5987A0@VI1PR0402MB3485.eurprd04.prod.outlook.com>
On Mon, 25 Feb 2019 at 14:03, Horia Geanta <horia.geanta@nxp.com> wrote:
> The code looks *very* similar to what was developed by NXP.
> Why have you stripped off the S-O-Bs?
Hi Horia,
Apologies, I was struggling to find any guidance about what to do with
the tags when upstreaming changes. I will add them in the next
version.
Thanks,
Chris
next prev parent reply other threads:[~2019-02-25 14:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 10:06 [RFC 0/4] crypto: caam - Add i.MX8MQ support spencercw
2019-02-22 10:06 ` [RFC 1/4] crypto: caam - fix detection of i.MX8 SoC spencercw
2019-02-25 7:50 ` Chris Spencer
2019-02-22 10:06 ` [RFC 2/4] crypto: caam - do not initialise clocks on the i.MX8 spencercw
2019-02-22 10:06 ` [RFC 3/4] crypto: caam - correct DMA address size for " spencercw
2019-02-22 10:06 ` [RFC 4/4] crypto: caam - use job ring for RNG instantiation instead of DECO spencercw
2019-02-25 14:22 ` Horia Geanta
2019-02-25 14:36 ` Chris Spencer
2019-02-26 14:53 ` Horia Geanta
2019-02-26 16:24 ` Chris Spencer
2019-02-28 11:33 ` Chris Spencer
2019-03-04 18:13 ` Horia Geanta
2019-03-05 8:54 ` Chris Spencer
2019-02-25 14:03 ` [RFC 0/4] crypto: caam - Add i.MX8MQ support Horia Geanta
2019-02-25 14:17 ` Chris Spencer [this message]
2019-02-25 19:28 ` Chris Spencer
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=CAGUNXRTe_G91TN-3qP-TAACB6kLXgJn-on5VGCJWbMqrv+rBWw@mail.gmail.com \
--to=spencercw@gmail.com \
--cc=aymen.sghaier@nxp.com \
--cc=christopher.spencer@sea.co.uk \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.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.