[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200504050001.GC1375924@vkoul-mobl>
Date: Mon, 4 May 2020 10:30:01 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Cristian Ciocaltea <cristian.ciocaltea@...il.com>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
Andreas Färber <afaerber@...e.de>,
Dan Williams <dan.j.williams@...el.com>,
dmaengine@...r.kernel.org, linux-actions@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/1] dma: actions: Fix lockdep splat for owl-dma
Hi Cristian,
On 02-05-20, 20:35, Cristian Ciocaltea wrote:
> On Sat, May 02, 2020 at 05:53:33PM +0530, Vinod Koul wrote:
> > Hi Cristian,
> >
> > On 29-04-20, 18:28, Cristian Ciocaltea wrote:
> > > When the kernel is built with lockdep support and the owl-dma driver is
> > > used, the following message is shown:
> >
> > First the patch title needs upate, we describe the patch in the title
> > and not the cause. So use correct lock, or use od lock might be better
> > titles, pls revise.
> >
> > Second, the susbsystem is named dmaengine:... not dma:.. You can always
> > check that by using git log on the respective file
> >
> > Pls do add fixes and further acks received on next iteration.
> >
>
> Hi Vinod,
>
> Thank you for reviewing and sorry for the mistakes! I'll be more careful
> next time with all those details.
No issues, we do learn a bit everytime :)
>
> I've submitted the updated patch: [PATCH v4 1/1] dmaengine: owl: Use
> correct lock in owl_dma_get_pchan()
Thanks
--
~Vinod
Powered by blists - more mailing lists