[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DBBPR08MB45385F76B0564DE1D8FFB6BFF7D7A@DBBPR08MB4538.eurprd08.prod.outlook.com>
Date: Mon, 16 Oct 2023 02:59:31 +0000
From: Justin He <Justin.He@....com>
To: Christoph Hellwig <hch@....de>, Robin Murphy <Robin.Murphy@....com>
CC: Marek Szyprowski <m.szyprowski@...sung.com>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v2] dma-mapping: fix dma_addressing_limited if
dma_range_map can't cover all system RAM
Hi,
> -----Original Message-----
> From: Christoph Hellwig <hch@....de>
> Sent: Wednesday, October 11, 2023 1:11 PM
> To: Robin Murphy <Robin.Murphy@....com>
> Cc: Christoph Hellwig <hch@....de>; Justin He <Justin.He@....com>; Marek
> Szyprowski <m.szyprowski@...sung.com>; iommu@...ts.linux.dev;
> linux-kernel@...r.kernel.org
> Subject: Re: [PATCH v2] dma-mapping: fix dma_addressing_limited if
> dma_range_map can't cover all system RAM
>
>
[snip]
> Ah, indeed, I somehw misremembered calling it in the mapping code.
>
> Justing, can you still respin this a bit, add a prep patch to move
> dma_addressing_limited so that it is exported instead of the new low-level
> helper, and fix up coding style issues like the overly long lines of possible? If
> it's not perfect I'll fix up the rest later.
Sure, thanks for the suggestion.
--
Cheers,
Justin (Jia He)
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Powered by blists - more mailing lists