From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
jacopo+renesas-AW8dsiIh9cEdnm+yROfE0A@public.gmane.org,
hch-jcswGhMUV9g@public.gmane.org
Subject: Re: [PATCH] dma-coherent: Clarify dma_mmap_from_dev_coherent documentation
Date: Mon, 23 Apr 2018 14:56:08 +0200 [thread overview]
Message-ID: <20180423125608.GA8824@lst.de> (raw)
In-Reply-To: <900c26f7cc33792c685fd3390c06e60ac81885de.1523296733.git.robin.murphy-5wv7dgnIgG8@public.gmane.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.
prev parent reply other threads:[~2018-04-23 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 17:59 [PATCH] dma-coherent: Clarify dma_mmap_from_dev_coherent documentation Robin Murphy
[not found] ` <900c26f7cc33792c685fd3390c06e60ac81885de.1523296733.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2018-04-23 12:56 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180423125608.GA8824@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jacopo+renesas-AW8dsiIh9cEdnm+yROfE0A@public.gmane.org \
--cc=robin.murphy-5wv7dgnIgG8@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox