From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Palmer Dabbelt <palmer-SpMDHPYPyPbQT0dZR+AlfA@public.gmane.org>
Cc: linux-riscv-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: add swiotlb support for riscv
Date: Sat, 19 May 2018 08:35:34 +0200 [thread overview]
Message-ID: <20180519063534.GA17809@lst.de> (raw)
In-Reply-To: <mhng-268a981e-4623-4e88-baf3-09cb0fbaca25@palmer-si-x1c4>
On Fri, May 18, 2018 at 04:31:36PM -0700, Palmer Dabbelt wrote:
>> http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/riscv-swiotlb
>
> Ah, great! This is much cleaner than our current implementation, which
> isn't based on the generic stuff :). I'm happy to have these through that
> tree if it makes the merging easier, feel free to add an
>
> Acked-by: Palmer Dabbelt <palmer-SpMDHPYPyPbQT0dZR+AlfA@public.gmane.org>
>
> and/or a
>
> Reviewed-by: Palmer Dabbelt <palmer-SpMDHPYPyPbQT0dZR+AlfA@public.gmane.org>
>
> on all 3 of these patches if that helps. I'm going to park them on my
> next-swiotlb branch so I can use them, but I won't submit them myself
> unless someone says something.
I think it is indeed easiest if I pull them into the dma-mapping tree.
Feel free the keep them in a riscv branch as well, but remember that
they depend on other patches in the dma-mapping tree that consolidate
the SWIOTLB Kconfig symbol.
prev parent reply other threads:[~2018-05-19 6:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 14:42 add swiotlb support for riscv Christoph Hellwig
[not found] ` <20180516144302.823-1-hch-jcswGhMUV9g@public.gmane.org>
2018-05-16 14:43 ` [PATCH 1/3] riscv: simplify Kconfig magic for 32-bit vs 64-bit kernels Christoph Hellwig
2018-05-16 14:43 ` [PATCH 2/3] riscv: only enable ZONE_DMA32 for 64-bit Christoph Hellwig
2018-05-16 14:43 ` [PATCH 3/3] riscv: add swiotlb support Christoph Hellwig
2018-05-18 23:31 ` add swiotlb support for riscv Palmer Dabbelt
2018-05-19 6:35 ` 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=20180519063534.GA17809@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-riscv-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=palmer-SpMDHPYPyPbQT0dZR+AlfA@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;
as well as URLs for NNTP newsgroup(s).