[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<SEYPR06MB62784DFD5EBBA85361C80A068293A@SEYPR06MB6278.apcprd06.prod.outlook.com>
Date: Fri, 15 Dec 2023 14:24:48 +0000
From: "Joakim Zhang" <joakim.zhang@...tech.com>
To: Christoph Hellwig <hch@....de>
CC: "m.szyprowski@...sung.com" <m.szyprowski@...sung.com>,
"robin.murphy@....com" <robin.murphy@....com>, "iommu@...ts.linux.dev"
<iommu@...ts.linux.dev>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, cix-kernel-upstream
<cix-kernel-upstream@...tech.com>
Subject: RE: [PATCH V2] dma-mapping: Set dma_mem pointer as NULL after it's
freed
Hi Christoph Hellwig,
> -----Original Message-----
> From: Christoph Hellwig <hch@....de>
> Sent: Friday, December 15, 2023 7:32 PM
> To: Joakim Zhang <joakim.zhang@...tech.com>
> Cc: hch@....de; m.szyprowski@...sung.com; robin.murphy@....com;
> iommu@...ts.linux.dev; linux-kernel@...r.kernel.org; cix-kernel-upstream
> <cix-kernel-upstream@...tech.com>
> Subject: Re: [PATCH V2] dma-mapping: Set dma_mem pointer as NULL after
> it's freed
>
> I've applied this after fixing the whitespace errors.
>
> But we really need to get remoteporc off messing with the reserved regions
> itself and retire this API entirely.
Indeed, I met this issue when debugging remoteproc, this API maybe useful since some system would not support device tree, but still want to reserve memory in the driver.
Powered by blists - more mailing lists