Re: [PATCH 0/4] add CAAM DMA memcpy driver

Re: [PATCH 0/4] add CAAM DMA memcpy driver

[Horia Geantă]

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

RE: [PATCH 0/4] add CAAM DMA memcpy driver

[Koul, Vinod]

> 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

Re: [PATCH 0/4] add CAAM DMA memcpy driver

[Horia Geantă]

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

Re: [PATCH 0/4] add CAAM DMA memcpy driver

[Vinod Koul]

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