From: Christoph Hellwig <hch@lst.de>
To: Michal Simek <michal.simek@xilinx.com>
Cc: Christoph Hellwig <hch@lst.de>, Michal Simek <monstr@monstr.eu>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: use the generic dma-noncoherent code for microblaze
Date: Fri, 20 Jul 2018 15:26:12 +0200 [thread overview]
Message-ID: <20180720132612.GA15416@lst.de> (raw)
In-Reply-To: <434e2ef1-3e3f-46d5-a7d1-62ed0e217da0@xilinx.com>
On Fri, Jul 20, 2018 at 02:33:44PM +0200, Michal Simek wrote:
> Hi,
>
> On 19.7.2018 14:54, Christoph Hellwig wrote:
> > Hi Michal,
> >
> > can you review these patches to switch microblaze to use the generic
> > dma-noncoherent code? All the requirements are in mainline already
> > and we've switched various architectures over to it already.
> >
>
> I can't see any issue with them.
> Both applied to next.
!
prev parent reply other threads:[~2018-07-20 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 12:54 use the generic dma-noncoherent code for microblaze Christoph Hellwig
2018-07-19 12:54 ` [PATCH 1/2] microblaze: use generic dma_noncoherent_ops Christoph Hellwig
2018-07-19 12:54 ` [PATCH 2/2] microblaze: remove consistent_sync and consistent_sync_page Christoph Hellwig
2018-07-20 12:33 ` use the generic dma-noncoherent code for microblaze Michal Simek
2018-07-20 13:26 ` 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=20180720132612.GA15416@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--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).