From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Mikko Perttunen
<mperttunen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 2/2] iommu: Add dummy implementations for !IOMMU_IOVA
Date: Wed, 22 Mar 2017 15:55:30 +0100 [thread overview]
Message-ID: <20170322145530.GC7315@8bytes.org> (raw)
In-Reply-To: <20170320191431.GF14787-EkSeR96xj6Pcmrwk2tT4+A@public.gmane.org>
Hi Thierry
On Mon, Mar 20, 2017 at 08:14:31PM +0100, Thierry Reding wrote:
> I've got a series of patches that I'd like to merge for v4.12 that have
> a build-time dependency on this patch. It would therefore be great to
> get your Acked-by on this so that I can merge it through the DRM tree
> with the rest of the patches. I can provide a stable branch with only
> this patch for you to pull into the IOMMU tree.
I applied both patches to my 'core' branch. There is not much in there
yet besides your patches, so you can easily pull that branch in once it
is published (later today).
Joerg
next prev parent reply other threads:[~2017-03-22 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 19:11 [PATCH 1/2] MAINTAINERS: Add related headers to IOMMU section Thierry Reding
[not found] ` <20170320191128.26474-1-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-20 19:11 ` [PATCH 2/2] iommu: Add dummy implementations for !IOMMU_IOVA Thierry Reding
[not found] ` <20170320191128.26474-2-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-20 19:14 ` Thierry Reding
[not found] ` <20170320191431.GF14787-EkSeR96xj6Pcmrwk2tT4+A@public.gmane.org>
2017-03-22 14:55 ` Joerg Roedel [this message]
[not found] ` <20170322145530.GC7315-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-03-22 18:07 ` Thierry Reding
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=20170322145530.GC7315@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mperttunen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@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;
as well as URLs for NNTP newsgroup(s).