From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] dma-coherent: Clarify dma_mmap_from_dev_coherent documentation Date: Mon, 23 Apr 2018 14:56:08 +0200 Message-ID: <20180423125608.GA8824@lst.de> References: <900c26f7cc33792c685fd3390c06e60ac81885de.1523296733.git.robin.murphy@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <900c26f7cc33792c685fd3390c06e60ac81885de.1523296733.git.robin.murphy-5wv7dgnIgG8@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Robin Murphy Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, jacopo+renesas-AW8dsiIh9cEdnm+yROfE0A@public.gmane.org, hch-jcswGhMUV9g@public.gmane.org List-Id: iommu@lists.linux-foundation.org On Mon, Apr 09, 2018 at 06:59:14PM +0100, Robin Murphy wrote: > The use of "correctly mapped" here is misleading, since it can give the > wrong expectation in the case that the memory *should* have been mapped > from the per-device pool, but doing so failed for other reasons. Thanks, applied to the dma-mapping tree for 4.17.