devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: "Horia Geantă" <horia.geanta@nxp.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Dan Douglass <dan.douglass@nxp.com>,
	Rob Herring <robh+dt@kernel.org>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/4] crypto: caam - add Job Ring support for DPAA2 parts
Date: Tue, 25 Jul 2017 21:50:02 +0800	[thread overview]
Message-ID: <20170725135000.GC29754@dragon> (raw)
In-Reply-To: <VI1PR0401MB2591E386907CD8EA92DED08498B80@VI1PR0401MB2591.eurprd04.prod.outlook.com>

On Tue, Jul 25, 2017 at 01:31:52PM +0000, Horia Geantă wrote:
> On 7/25/2017 4:22 PM, Shawn Guo wrote:
> > 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.
> 
> Thanks for the clarification.
> 
> Do I have to re-post the DTS patches once the driver is accepted or a
> ping should suffice or...?

A ping is sufficient.

Shawn

  reply	other threads:[~2017-07-25 13:50 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 2/4] arm64: dts: freescale: ls208xa: share aliases node Horia Geantă
2017-07-18 15:30 ` [PATCH 4/4] arm64: dts: freescale: ls1088a: add crypto node Horia Geantă
     [not found] ` <20170718153050.15330-1-horia.geanta-3arQi8VN3Tc@public.gmane.org>
2017-07-18 15:30   ` [PATCH 1/4] crypto: caam/jr - add support for DPAA2 parts Horia Geantă
     [not found]     ` <20170718153050.15330-2-horia.geanta-3arQi8VN3Tc@public.gmane.org>
2017-08-03  6:09       ` Herbert Xu
2017-07-18 15:30   ` [PATCH 3/4] arm64: dts: freescale: ls208xa: add crypto node Horia Geantă
2017-07-25 13:21   ` [PATCH 0/4] crypto: caam - add Job Ring support for DPAA2 parts Shawn Guo
2017-07-25 13:31     ` Horia Geantă
2017-07-25 13:50       ` Shawn Guo [this message]
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=20170725135000.GC29754@dragon \
    --to=shawnguo@kernel.org \
    --cc=dan.douglass@nxp.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --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=mark.rutland@arm.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).