From: Michal Simek <monstr@monstr.eu>
To: Christoph Hellwig <hch@infradead.org>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: convert microblaze to the generic dma remap allocator
Date: Mon, 26 Aug 2019 09:13:54 +0200 [thread overview]
Message-ID: <8da3e42e-6c13-104f-b985-d04be1eca018@monstr.eu> (raw)
In-Reply-To: <20190826070258.GA31420@infradead.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 771 bytes --]
Hi,
On 26. 08. 19 9:02, Christoph Hellwig wrote:
> On Wed, Aug 14, 2019 at 04:03:46PM +0200, Christoph Hellwig wrote:
>> Hi Michal,
>>
>> can you take a look at this patch that moves microblaze over to the
>> generic DMA remap allocator? I've been trying to slowly get all
>> architectures over to the generic code, and microblaze is one that
>> seems very straightfoward to convert.
>
> Michal, any chance you could look over this series?
>
let me take a look.
M
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-08-26 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 14:03 convert microblaze to the generic dma remap allocator Christoph Hellwig
2019-08-14 14:03 ` [PATCH 1/2] microblaze/nommu: use the generic uncached segment support Christoph Hellwig
2019-08-14 14:03 ` [PATCH 2/2] microblaze: use the generic dma coherent remap allocator Christoph Hellwig
2019-08-26 7:02 ` convert microblaze to the generic dma " Christoph Hellwig
2019-08-26 7:13 ` Michal Simek [this message]
2019-08-30 10:58 ` Michal Simek
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=8da3e42e-6c13-104f-b985-d04be1eca018@monstr.eu \
--to=monstr@monstr.eu \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.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).