From: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
To: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Sakari Ailus
<sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
"jian.xu.zheng-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
<jian.xu.zheng-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [PATCH 0/4] Separate the IOVA library from the intel-iommu driver
Date: Mon, 14 Sep 2015 19:17:57 +0100 [thread overview]
Message-ID: <55F70F55.80402@arm.com> (raw)
In-Reply-To: <1438089947.26913.155.camel-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Hi David,
On 28/07/15 14:25, David Woodhouse wrote:
> On Mon, 2015-07-13 at 14:31 +0300, Sakari Ailus wrote:
>> Hi folks,
>>
>> This set separates the IOVA library from the intel-iommu driver, and makes
>> it usable for other implementations (such as DMA mapping) as well.
>
> Thanks. I've applied patches ##1-3 to my tree. The fourth patch ideally
> wants to go elsewhere.
>
This doesn't seem to have made 4.3-rc1, despite having been in -next for
a while. Were you planning to push it for 4.3, or is it waiting on
further development?
Thanks,
Robin.
prev parent reply other threads:[~2015-09-14 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 11:31 [PATCH 0/4] Separate the IOVA library from the intel-iommu driver Sakari Ailus
[not found] ` <1436787091-11943-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-07-13 11:31 ` [PATCH 1/4] iommu: iova: Move iova cache management to the iova library Sakari Ailus
2015-07-13 11:31 ` [PATCH 2/4] iommu: iova: Export symbols Sakari Ailus
2015-07-13 11:31 ` [PATCH 3/4] iommu: Make the iova library a module Sakari Ailus
2015-07-13 11:31 ` [PATCH 4/4] mm: EXPORT_SYMBOL_GPL(find_vm_area); Sakari Ailus
2015-07-28 13:25 ` [PATCH 0/4] Separate the IOVA library from the intel-iommu driver David Woodhouse
[not found] ` <1438089947.26913.155.camel-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-09-14 18:17 ` Robin Murphy [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=55F70F55.80402@arm.com \
--to=robin.murphy-5wv7dgnigg8@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jian.xu.zheng-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=sakari.ailus-VuQAYsv1563Yd54FQh9/CA@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