linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] crypto: caam - add Job Ring support for DPAA2 parts
Date: Tue, 25 Jul 2017 21:21:30 +0800	[thread overview]
Message-ID: <20170725132129.GB29754@dragon> (raw)
In-Reply-To: <20170718153050.15330-1-horia.geanta@nxp.com>

On Tue, Jul 18, 2017 at 06:30:46PM +0300, Horia Geant? wrote:
> This patch set adds support for CAAM's legacy Job Ring backend / interface
> on platforms having DPAA2 (Datapath Acceleration Architecture v2), like
> LS1088A or LS2088A.
> 
> I would like to get the DT patches through the crypto list (to make sure
> they don't end up merged before driver support).

Unless it's really urgent (usually critical bug fix), the DTS patches
should go through arm-soc tree.  We usually take DTS patches after the
driver counterpart has been accepted by subsystem maintainers, or in the
best case, has landed on mainline.

Shawn

  parent reply	other threads:[~2017-07-25 13:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 15:30 [PATCH 0/4] crypto: caam - add Job Ring support for DPAA2 parts Horia Geantă
2017-07-18 15:30 ` [PATCH 1/4] crypto: caam/jr - add " Horia Geantă
2017-08-03  6:09   ` Herbert Xu
2017-07-18 15:30 ` [PATCH 2/4] arm64: dts: freescale: ls208xa: share aliases node Horia Geantă
2017-07-18 15:30 ` [PATCH 3/4] arm64: dts: freescale: ls208xa: add crypto node Horia Geantă
2017-07-18 15:30 ` [PATCH 4/4] arm64: dts: freescale: ls1088a: " Horia Geantă
2017-07-25 13:21 ` Shawn Guo [this message]
2017-07-25 13:31   ` [PATCH 0/4] crypto: caam - add Job Ring support for DPAA2 parts Horia Geantă
2017-07-25 13:50     ` Shawn Guo
2017-08-03  8:07       ` Horia Geantă
2017-08-05  1:54 ` Shawn Guo

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=20170725132129.GB29754@dragon \
    --to=shawnguo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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).