From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: robin.murphy@arm.com, m.szyprowski@samsung.com,
vdumpa@nvidia.com, linux@armlinux.org.uk,
catalin.marinas@arm.com, will.deacon@arm.com, chris@zankel.net,
jcmvbkbc@gmail.com, joro@8bytes.org, dwmw2@infradead.org,
tony@atomide.com, akpm@linux-foundation.org,
sfr@canb.auug.org.au, treding@nvidia.com, keescook@chromium.org,
iamjoonsoo.kim@lge.com, wsa+renesas@sang-engineering.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-xtensa@linux-xtensa.org,
iommu@lists.linux-foundation.org, dann.frazier@canonical.com
Subject: Re: [PATCH v3 0/2] Optimize dma_*_from_contiguous calls
Date: Wed, 29 May 2019 16:06:19 -0700 [thread overview]
Message-ID: <20190529230618.GC17556@Asurada-Nvidia.nvidia.com> (raw)
In-Reply-To: <20190528060424.GA11521@lst.de>
On Tue, May 28, 2019 at 08:04:24AM +0200, Christoph Hellwig wrote:
> Thanks,
>
> applied to dma-mapping for-next.
>
> Can you also send a conversion of drivers/iommu/dma-iommu.c to your
> new helpers against this tree?
>
> http://git.infradead.org/users/hch/dma-mapping.git/shortlog/refs/heads/for-next
I can. There is a reported regression with !CONFIG_DMA_CMA now
so I will do that after a fix is merged and the whole thing is
stable.
Thank you
prev parent reply other threads:[~2019-05-29 23:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 4:06 [PATCH v3 0/2] Optimize dma_*_from_contiguous calls Nicolin Chen
2019-05-24 4:06 ` [PATCH v3 1/2] dma-contiguous: Abstract dma_{alloc,free}_contiguous() Nicolin Chen
2019-05-29 18:35 ` Nathan Chancellor
2019-05-29 22:48 ` Nicolin Chen
2019-07-25 16:06 ` Ezequiel Garcia
2019-07-25 16:50 ` Nicolin Chen
2019-07-25 17:31 ` Dafna Hirschfeld
2019-07-25 23:42 ` Nicolin Chen
2019-05-24 4:06 ` [PATCH v3 2/2] dma-contiguous: Use fallback alloc_pages for single pages Nicolin Chen
2019-05-24 16:16 ` Ira Weiny
2019-05-27 10:55 ` Nicolin Chen
2019-05-24 20:03 ` [PATCH v3 0/2] Optimize dma_*_from_contiguous calls dann frazier
2019-05-28 6:04 ` Christoph Hellwig
2019-05-29 23:06 ` Nicolin Chen [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=20190529230618.GC17556@Asurada-Nvidia.nvidia.com \
--to=nicoleotsuka@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=chris@zankel.net \
--cc=dann.frazier@canonical.com \
--cc=dwmw2@infradead.org \
--cc=hch@lst.de \
--cc=iamjoonsoo.kim@lge.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jcmvbkbc@gmail.com \
--cc=joro@8bytes.org \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=sfr@canb.auug.org.au \
--cc=tony@atomide.com \
--cc=treding@nvidia.com \
--cc=vdumpa@nvidia.com \
--cc=will.deacon@arm.com \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).