* Re: [PATCH 0/4] add CAAM DMA memcpy driver [not found] <20171026100008.32169-1-radu.alexe@nxp.com> @ 2017-10-27 11:00 ` Horia Geantă 2017-10-27 11:35 ` Koul, Vinod 0 siblings, 1 reply; 4+ messages in thread From: Horia Geantă @ 2017-10-27 11:00 UTC (permalink / raw) To: Radu Andrei Alexe, vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org, herbert-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public.gmane.org, davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org, Dan Douglass, shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org Cc: dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On 10/26/2017 1:01 PM, Radu Alexe wrote: > This patch-set introduces a new DMA memcpy driver based on the DMA > capabilities of the CAAM crypto engine. Because of this dependency the > included commits target various parts of the kernel tree. I don't see the patches on any of the mail lists. If they are moderated, I would expect this to be mentioned in the MAINTAINERS file. > > Patch 1. > Since the CAAM DMA driver is a platform driver it is enabled by a new node > in the device tree. This commit adds documentation for the device tree > bindings. > > Patch 2. > This patch adds the "caam-dma" node in the fsl-ls1012a.dtsi file. > > Patch 3. > This commit adds various capabilities in the JR driver of the CAAM that is > used by the CAAM DMA driver. > > Patch 4. > Adds the CAAM DMA memcpy driver. > > Patch 1 and 3 should be merged by the crypto maintainers, patch 2 by > devicetree maintainers and patch 4 by the DMA maintainers. I would go with all the patches through the dmaengine tree. Horia -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: [PATCH 0/4] add CAAM DMA memcpy driver 2017-10-27 11:00 ` [PATCH 0/4] add CAAM DMA memcpy driver Horia Geantă @ 2017-10-27 11:35 ` Koul, Vinod 2017-10-27 12:20 ` Horia Geantă 0 siblings, 1 reply; 4+ messages in thread From: Koul, Vinod @ 2017-10-27 11:35 UTC (permalink / raw) To: Horia Geantă, Radu Andrei Alexe, herbert@gondor.apana.org.au, davem@davemloft.net, Dan Douglass, shawnguo@kernel.org Cc: dmaengine@vger.kernel.org, linux-crypto@vger.kernel.org, devicetree@vger.kernel.org > On 10/26/2017 1:01 PM, Radu Alexe wrote: > > This patch-set introduces a new DMA memcpy driver based on the DMA > > capabilities of the CAAM crypto engine. Because of this dependency the > > included commits target various parts of the kernel tree. > I don't see the patches on any of the mail lists. > If they are moderated, I would expect this to be mentioned in the > MAINTAINERS file. > > > > > Patch 1. > > Since the CAAM DMA driver is a platform driver it is enabled by a new node > > in the device tree. This commit adds documentation for the device tree > > bindings. > > > > Patch 2. > > This patch adds the "caam-dma" node in the fsl-ls1012a.dtsi file. > > > > Patch 3. > > This commit adds various capabilities in the JR driver of the CAAM that is > > used by the CAAM DMA driver. > > > > Patch 4. > > Adds the CAAM DMA memcpy driver. > > > > Patch 1 and 3 should be merged by the crypto maintainers, patch 2 by > > devicetree maintainers and patch 4 by the DMA maintainers. > I would go with all the patches through the dmaengine tree. Good call, but no one CCed dmaengine folks on this series! -- ~Vinod ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 0/4] add CAAM DMA memcpy driver 2017-10-27 11:35 ` Koul, Vinod @ 2017-10-27 12:20 ` Horia Geantă 2017-10-30 13:10 ` Vinod Koul 0 siblings, 1 reply; 4+ messages in thread From: Horia Geantă @ 2017-10-27 12:20 UTC (permalink / raw) To: Koul, Vinod, Radu Andrei Alexe, herbert@gondor.apana.org.au, davem@davemloft.net, Dan Douglass, shawnguo@kernel.org Cc: dmaengine@vger.kernel.org, linux-crypto@vger.kernel.org, devicetree@vger.kernel.org On 10/27/2017 2:36 PM, Koul, Vinod wrote: >> On 10/26/2017 1:01 PM, Radu Alexe wrote: >>> This patch-set introduces a new DMA memcpy driver based on the DMA >>> capabilities of the CAAM crypto engine. Because of this dependency the >>> included commits target various parts of the kernel tree. >> I don't see the patches on any of the mail lists. >> If they are moderated, I would expect this to be mentioned in the >> MAINTAINERS file. >> >>> >>> Patch 1. >>> Since the CAAM DMA driver is a platform driver it is enabled by a new node >>> in the device tree. This commit adds documentation for the device tree >>> bindings. >>> >>> Patch 2. >>> This patch adds the "caam-dma" node in the fsl-ls1012a.dtsi file. >>> >>> Patch 3. >>> This commit adds various capabilities in the JR driver of the CAAM that is >>> used by the CAAM DMA driver. >>> >>> Patch 4. >>> Adds the CAAM DMA memcpy driver. >>> >>> Patch 1 and 3 should be merged by the crypto maintainers, patch 2 by >>> devicetree maintainers and patch 4 by the DMA maintainers. >> I would go with all the patches through the dmaengine tree. > > Good call, but no one CCed dmaengine folks on this series! > I see dmaengine@vger.kernel.org Cc-ed on both cover letter and all four patches. It might be that the sender (Radu) is not subscribed and messages are awaiting moderators' approval. Horia ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 0/4] add CAAM DMA memcpy driver 2017-10-27 12:20 ` Horia Geantă @ 2017-10-30 13:10 ` Vinod Koul 0 siblings, 0 replies; 4+ messages in thread From: Vinod Koul @ 2017-10-30 13:10 UTC (permalink / raw) To: Horia Geantă Cc: Radu Andrei Alexe, herbert@gondor.apana.org.au, davem@davemloft.net, Dan Douglass, shawnguo@kernel.org, dmaengine@vger.kernel.org, linux-crypto@vger.kernel.org, devicetree@vger.kernel.org On Fri, Oct 27, 2017 at 12:20:32PM +0000, Horia Geantă wrote: > On 10/27/2017 2:36 PM, Koul, Vinod wrote: > >> On 10/26/2017 1:01 PM, Radu Alexe wrote: > >>> This patch-set introduces a new DMA memcpy driver based on the DMA > >>> capabilities of the CAAM crypto engine. Because of this dependency the > >>> included commits target various parts of the kernel tree. > >> I don't see the patches on any of the mail lists. > >> If they are moderated, I would expect this to be mentioned in the > >> MAINTAINERS file. > >> > >>> > >>> Patch 1. > >>> Since the CAAM DMA driver is a platform driver it is enabled by a new node > >>> in the device tree. This commit adds documentation for the device tree > >>> bindings. > >>> > >>> Patch 2. > >>> This patch adds the "caam-dma" node in the fsl-ls1012a.dtsi file. > >>> > >>> Patch 3. > >>> This commit adds various capabilities in the JR driver of the CAAM that is > >>> used by the CAAM DMA driver. > >>> > >>> Patch 4. > >>> Adds the CAAM DMA memcpy driver. > >>> > >>> Patch 1 and 3 should be merged by the crypto maintainers, patch 2 by > >>> devicetree maintainers and patch 4 by the DMA maintainers. > >> I would go with all the patches through the dmaengine tree. > > > > Good call, but no one CCed dmaengine folks on this series! > > > I see dmaengine@vger.kernel.org Cc-ed on both cover letter and all four > patches. > It might be that the sender (Radu) is not subscribed and messages are > awaiting moderators' approval. I think vger lists are open, maybe sender has some issues with mail as they are still not in any archives.. -- ~Vinod ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-10-30 13:10 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20171026100008.32169-1-radu.alexe@nxp.com>
2017-10-27 11:00 ` [PATCH 0/4] add CAAM DMA memcpy driver Horia Geantă
2017-10-27 11:35 ` Koul, Vinod
2017-10-27 12:20 ` Horia Geantă
2017-10-30 13:10 ` Vinod Koul
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).