[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220623054211.GA12408@lst.de>
Date: Thu, 23 Jun 2022 07:42:11 +0200
From: Christoph Hellwig <hch@....de>
To: Mathieu Poirier <mathieu.poirier@...aro.org>
Cc: Christoph Hellwig <hch@....de>,
Mark-PK Tsai <mark-pk.tsai@...iatek.com>,
bjorn.andersson@...aro.org, robin.murphy@....com,
m.szyprowski@...sung.com, matthias.bgg@...il.com,
linux-remoteproc@...r.kernel.org, linux-kernel@...r.kernel.org,
iommu@...ts.linux-foundation.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, yj.chiang@...iatek.com
Subject: Re: [PATCH 0/2] dma-mapping, remoteproc: Fix dma_mem leak after
rproc_shutdown
On Wed, Jun 22, 2022 at 10:25:40AM -0600, Mathieu Poirier wrote:
> On Sat, Apr 23, 2022 at 07:46:50PM +0200, Christoph Hellwig wrote:
> > Sigh. In theory drivers should never declare coherent memory like
> > this, and there has been some work to fix remoteproc in that regard.
> >
> > But I guess until that is merged we'll need somthing like this fix.
>
> Should I take this in the remoteproc tree? If so, can I get an RB?
Reluctantly-Acked-by: Christoph Hellwig <hch@....de>
Powered by blists - more mailing lists