From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vinod Koul Subject: Re: [PATCH 0/4] add CAAM DMA memcpy driver Date: Mon, 30 Oct 2017 18:40:04 +0530 Message-ID: <20171030131004.GD3187@localhost> References: <20171026100008.32169-1-radu.alexe@nxp.com> <8D3F6266AEB6384E807C6FFC6FE195E333C52210@BGSMSX107.gar.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org To: Horia =?utf-8?Q?Geant=C4=83?= 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" List-Id: 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