From: joro@8bytes.org (joro at 8bytes.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] Generic IOMMU page table framework
Date: Mon, 19 Jan 2015 15:01:06 +0100 [thread overview]
Message-ID: <20150119140106.GM6343@8bytes.org> (raw)
In-Reply-To: <2897578.zknPhjxUSB@avalon>
On Mon, Jan 19, 2015 at 03:56:42PM +0200, Laurent Pinchart wrote:
> Yes, and I've rebased them (or actually it, it's a single patch) on v2. I
> haven't had time to test the result yet, I'll try to do so later tonight or
> tomorrow.
Great! Would be good if this can go upstream with more than one user.
Joerg
next prev parent reply other threads:[~2015-01-19 14:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 13:54 [PATCH v2 0/5] Generic IOMMU page table framework Will Deacon
2015-01-09 13:54 ` [PATCH v2 1/5] iommu: introduce generic page table allocation framework Will Deacon
2015-01-09 13:54 ` [PATCH v2 2/5] iommu: add ARM LPAE page table allocator Will Deacon
2015-01-09 13:54 ` [PATCH v2 3/5] iommu: add self-consistency tests to ARM LPAE IO " Will Deacon
2015-01-09 13:54 ` [PATCH v2 4/5] iommu/arm-smmu: make use of generic LPAE allocator Will Deacon
2015-01-09 13:54 ` [PATCH v2 5/5] iommu: io-pgtable-arm: add non-secure quirk Will Deacon
2015-01-16 14:01 ` [PATCH v2 0/5] Generic IOMMU page table framework Will Deacon
2015-01-19 13:09 ` joro at 8bytes.org
2015-01-19 13:18 ` Will Deacon
2015-01-19 13:56 ` Laurent Pinchart
2015-01-19 14:01 ` joro at 8bytes.org [this message]
2015-01-20 16:30 ` [PATCH v2] iommu/ipmmu-vmsa: Use the ARM LPAE page table allocator Laurent Pinchart
2015-01-21 14:44 ` Will Deacon
2015-01-21 14:58 ` Laurent Pinchart
2015-01-21 15:05 ` joro at 8bytes.org
2015-01-21 15:07 ` Laurent Pinchart
2015-01-21 15:27 ` joro at 8bytes.org
2015-01-21 15:31 ` Laurent Pinchart
2015-01-26 12:46 ` joro at 8bytes.org
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=20150119140106.GM6343@8bytes.org \
--to=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.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).