Linux IOMMU Development
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Cc: will.deacon-5wv7dgnIgG8@public.gmane.org,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
	dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 0/4] Genericise the IOVA allocator
Date: Mon, 19 Jan 2015 14:59:54 +0100	[thread overview]
Message-ID: <20150119135954.GL6343@8bytes.org> (raw)
In-Reply-To: <cover.1420822848.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>

On Mon, Jan 12, 2015 at 05:51:12PM +0000, Robin Murphy wrote:
> Robin Murphy (4):
>   iommu: allow building iova.c independently
>   iommu: consolidate IOVA allocator code
>   iommu: make IOVA domain low limit flexible
>   iommu: make IOVA domain page size explicit

Applied to core, thanks Robin.

      parent reply	other threads:[~2015-01-19 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12 17:51 [PATCH 0/4] Genericise the IOVA allocator Robin Murphy
     [not found] ` <cover.1420822848.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2015-01-12 17:51   ` [PATCH 1/4] iommu: allow building iova.c independently Robin Murphy
2015-01-12 17:51   ` [PATCH 2/4] iommu: consolidate IOVA allocator code Robin Murphy
2015-01-12 17:51   ` [PATCH 3/4] iommu: make IOVA domain low limit flexible Robin Murphy
2015-01-12 17:51   ` [PATCH 4/4] iommu: make IOVA domain page size explicit Robin Murphy
2015-01-19 13:59   ` Joerg Roedel [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=20150119135954.GL6343@8bytes.org \
    --to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=robin.murphy-5wv7dgnIgG8@public.gmane.org \
    --cc=thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
    --cc=will.deacon-5wv7dgnIgG8@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