From: Ley Foon Tan <ley.foon.tan@intel.com>
To: Christoph Hellwig <hch@lst.de>, Michal Simek <monstr@monstr.eu>
Cc: linux-mips@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: switch nios2 and microblaze to use the generic uncached segement support
Date: Fri, 14 Jun 2019 09:40:34 +0800 [thread overview]
Message-ID: <1560476434.21652.1.camel@intel.com> (raw)
In-Reply-To: <20190603065324.9724-1-hch@lst.de>
On Mon, 2019-06-03 at 08:53 +0200, Christoph Hellwig wrote:
> Hi all,
>
> can you take a look at this series? It switches niops2 and
> microblaze to
> use the generic dma layer support for uncached segements.
>
> The dma mapping for-next git tree that includes the support is
> available
> here:
>
> git://git.infradead.org/users/hch/dma-mapping.git for-next
>
> Gitweb:
>
> http://git.infradead.org/users/hch/dma-mapping.git/shortlog/refs/
> heads/for-next
>
Hi Christoph
Can this patch in http://git.infradead.org/users/hch/dma-mapping.git/sh
ortlog/refs/heads/for-next
[PATCH 1/2] nios2: use the generic uncached segment support in dma-
direct
Regards
Ley Foon
next prev parent reply other threads:[~2019-06-14 1:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 6:53 switch nios2 and microblaze to use the generic uncached segement support Christoph Hellwig
2019-06-03 6:53 ` [PATCH 1/2] nios2: use the generic uncached segment support in dma-direct Christoph Hellwig
2019-06-25 5:29 ` Ley Foon Tan
2019-06-25 5:52 ` Christoph Hellwig
2019-06-03 6:53 ` [PATCH 2/2] microblaze: " Christoph Hellwig
2019-06-14 1:40 ` Ley Foon Tan [this message]
2019-06-14 5:44 ` switch nios2 and microblaze to use the generic uncached segement support Christoph Hellwig
2019-06-14 6:11 ` Tan, Ley Foon
2019-06-14 6:52 ` hch
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=1560476434.21652.1.camel@intel.com \
--to=ley.foon.tan@intel.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=monstr@monstr.eu \
/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).