All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <oss@buserror.net>
To: "Horia Geantă" <horia.geanta@nxp.com>,
	"Herbert Xu" <herbert@gondor.apana.org.au>,
	"Roy Pledge" <roy.pledge@nxp.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	Cristian Stoica <cristian.stoica@nxp.com>,
	Dan Douglass <dan.douglass@nxp.com>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	Vakul Garg <vakul@nxp.com>,
	Alexandru Porosanu <alexandru.porosanu@nxp.com>
Subject: Re: [RFC 0/7] crypto: caam - add Queue Interface (QI) support
Date: Thu, 16 Mar 2017 15:49:30 -0500	[thread overview]
Message-ID: <1489697370.2944.46.camel@buserror.net> (raw)
In-Reply-To: <DB4PR04MB0847AD372AFF9510CDCA3ECD98260@DB4PR04MB0847.eurprd04.prod.outlook.com>

On Thu, 2017-03-16 at 14:13 +0000, Horia Geantă wrote:
> On 3/16/2017 10:43 AM, Herbert Xu wrote:
> > 
> > On Fri, Mar 03, 2017 at 04:52:06PM +0200, Horia Geantă wrote:
> > > 
> > > The patchset adds support for CAAM Queue Interface (QI), the additional
> > > interface (besides job ring) available for submitting jobs to the engine
> > > on platforms having DPAA (Datapath Acceleration Architecture).
> > > 
> > > Patches 1-4 are QMan dependencies.
> > > I would prefer to take them through the crypto tree,
> > > but I am open to suggestions.
> > > 
> > > Patch 5 adds a missing double inclusion guard in desc_constr.h.
> > > 
> > > Patch 6 adds the caam/qi job submission backend.
> > > 
> > > Patch 7 adds algorithms (ablkcipher and authenc) that run on top
> > > of caam/qi. For now, their priority is set lower than caam/jr.
> > I'm fine with the crypto bits.
> > 
> Herbert,
> 
> Thanks for the review.
> Should I submit formally, i.e. without the [RFC] prefix?
> 
> Scott, Roy,
> 
> Do you have any comments wrt. soc/qman patches or with them going
> through the crypto tree?

Going through the crypto tree is fine.

-Scott


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: oss@buserror.net (Scott Wood)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 0/7] crypto: caam - add Queue Interface (QI) support
Date: Thu, 16 Mar 2017 15:49:30 -0500	[thread overview]
Message-ID: <1489697370.2944.46.camel@buserror.net> (raw)
In-Reply-To: <DB4PR04MB0847AD372AFF9510CDCA3ECD98260@DB4PR04MB0847.eurprd04.prod.outlook.com>

On Thu, 2017-03-16 at 14:13 +0000, Horia Geant? wrote:
> On 3/16/2017 10:43 AM, Herbert Xu wrote:
> > 
> > On Fri, Mar 03, 2017 at 04:52:06PM +0200, Horia Geant? wrote:
> > > 
> > > The patchset adds support for CAAM Queue Interface (QI), the additional
> > > interface (besides job ring) available for submitting jobs to the engine
> > > on platforms having DPAA (Datapath Acceleration Architecture).
> > > 
> > > Patches 1-4 are QMan dependencies.
> > > I would prefer to take them through the crypto tree,
> > > but I am open to suggestions.
> > > 
> > > Patch 5 adds a missing double inclusion guard in desc_constr.h.
> > > 
> > > Patch 6 adds the caam/qi job submission backend.
> > > 
> > > Patch 7 adds algorithms (ablkcipher and authenc) that run on top
> > > of caam/qi. For now, their priority is set lower than caam/jr.
> > I'm fine with the crypto bits.
> > 
> Herbert,
> 
> Thanks for the review.
> Should I submit formally, i.e. without the [RFC] prefix?
> 
> Scott, Roy,
> 
> Do you have any comments wrt. soc/qman patches or with them going
> through the crypto tree?

Going through the crypto tree is fine.

-Scott

  reply	other threads:[~2017-03-16 20:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 14:52 [RFC 0/7] crypto: caam - add Queue Interface (QI) support Horia Geantă
2017-03-03 14:52 ` Horia Geantă
2017-03-03 14:52 ` [RFC 1/7] soc/qman: export volatile dequeue related structs Horia Geantă
2017-03-03 14:52   ` Horia Geantă
2017-03-03 14:52 ` [RFC 2/7] soc/qman: add dedicated channel ID for CAAM Horia Geantă
2017-03-03 14:52   ` Horia Geantă
2017-03-03 14:52 ` [RFC 3/7] soc/qman: export non-programmable FQD fields query Horia Geantă
2017-03-03 14:52   ` Horia Geantă
2017-03-03 14:52 ` [RFC 4/7] soc/qman: add helper functions needed by caam/qi driver Horia Geantă
2017-03-03 14:52   ` Horia Geantă
2017-03-16 20:39   ` Scott Wood
2017-03-16 20:39     ` Scott Wood
2017-03-03 14:52 ` [RFC 5/7] crypto: caam - avoid double inclusion in desc_constr.h Horia Geantă
2017-03-03 14:52   ` Horia Geantă
2017-03-03 14:52 ` [RFC 6/7] crypto: caam - add Queue Interface (QI) backend support Horia Geantă
2017-03-03 14:52   ` Horia Geantă
2017-03-03 14:52 ` [RFC 7/7] crypto: caam/qi - add ablkcipher and authenc algorithms Horia Geantă
2017-03-03 14:52   ` Horia Geantă
2017-03-16  8:42 ` [RFC 0/7] crypto: caam - add Queue Interface (QI) support Herbert Xu
2017-03-16  8:42   ` Herbert Xu
2017-03-16 14:13   ` Horia Geantă
2017-03-16 14:13     ` Horia Geantă
2017-03-16 20:49     ` Scott Wood [this message]
2017-03-16 20:49       ` Scott Wood

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=1489697370.2944.46.camel@buserror.net \
    --to=oss@buserror.net \
    --cc=alexandru.porosanu@nxp.com \
    --cc=claudiu.manoil@nxp.com \
    --cc=cristian.stoica@nxp.com \
    --cc=dan.douglass@nxp.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=roy.pledge@nxp.com \
    --cc=vakul@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.