From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Dongli Zhang <dongli.zhang@oracle.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
konrad.wilk@oracle.com, hch@lst.de, m.szyprowski@samsung.com,
robin.murphy@arm.com, joe.jin@oracle.com
Subject: Re: [PATCH v3 1/3] swiotlb: fix comment on swiotlb_bounce()
Date: Tue, 12 Feb 2019 13:47:13 -0500 [thread overview]
Message-ID: <20190212184708.GA19497@localhost.localdomain> (raw)
In-Reply-To: <1547795428-10595-1-git-send-email-dongli.zhang@oracle.com>
On Fri, Jan 18, 2019 at 03:10:26PM +0800, Dongli Zhang wrote:
> Fix the comment as swiotlb_bounce() is used to copy from original dma
> location to swiotlb buffer during swiotlb_tbl_map_single(), while to
> copy from swiotlb buffer to original dma location during
> swiotlb_tbl_unmap_single().
I queued up your patches in https://git.kernel.org/pub/scm/linux/kernel/git/konrad/swiotlb.git
>
> Signed-off-by: Dongli Zhang <dongli.zhang@oracle.com>
> ---
> kernel/dma/swiotlb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/dma/swiotlb.c b/kernel/dma/swiotlb.c
> index 1fb6fd6..1d8b377 100644
> --- a/kernel/dma/swiotlb.c
> +++ b/kernel/dma/swiotlb.c
> @@ -385,7 +385,7 @@ void __init swiotlb_exit(void)
> }
>
> /*
> - * Bounce: copy the swiotlb buffer back to the original dma location
> + * Bounce: copy the swiotlb buffer from or back to the original dma location
> */
> static void swiotlb_bounce(phys_addr_t orig_addr, phys_addr_t tlb_addr,
> size_t size, enum dma_data_direction dir)
> --
> 2.7.4
>
prev parent reply other threads:[~2019-02-12 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 7:10 [PATCH v3 1/3] swiotlb: fix comment on swiotlb_bounce() Dongli Zhang
2019-01-18 7:10 ` [PATCH v3 2/3] swiotlb: add debugfs to track swiotlb buffer usage Dongli Zhang
2019-01-18 7:10 ` [PATCH v3 3/3] swiotlb: checking whether swiotlb buffer is full with io_tlb_used Dongli Zhang
2019-02-12 18:47 ` Konrad Rzeszutek Wilk [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=20190212184708.GA19497@localhost.localdomain \
--to=konrad@darnok.org \
--cc=dongli.zhang@oracle.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=joe.jin@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
/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