From: Joerg Roedel <jroedel-l3A5Bk7waGM@public.gmane.org>
To: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [GIT PULL] iommu/arm-smmu: Updates for 4.6
Date: Thu, 25 Feb 2016 16:00:55 +0100 [thread overview]
Message-ID: <20160225150055.GC2280@suse.de> (raw)
In-Reply-To: <20160223123322.GL3966-5wv7dgnIgG8@public.gmane.org>
On Tue, Feb 23, 2016 at 12:33:22PM +0000, Will Deacon wrote:
> Please pull the following arm-smmu updates for 4.6. This lays the
> foundations for a functional IOMMU_DOMAIN_DMA for the two drivers,
> although we haven't yet thrown the switch since we need to ensure
> that the DMA ops all point in the right direction first. Hopefully we'll
> get that going for 4.7.
Pulled, thanks Will.
WARNING: multiple messages have this Message-ID (diff)
From: jroedel@suse.de (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] iommu/arm-smmu: Updates for 4.6
Date: Thu, 25 Feb 2016 16:00:55 +0100 [thread overview]
Message-ID: <20160225150055.GC2280@suse.de> (raw)
In-Reply-To: <20160223123322.GL3966@arm.com>
On Tue, Feb 23, 2016 at 12:33:22PM +0000, Will Deacon wrote:
> Please pull the following arm-smmu updates for 4.6. This lays the
> foundations for a functional IOMMU_DOMAIN_DMA for the two drivers,
> although we haven't yet thrown the switch since we need to ensure
> that the DMA ops all point in the right direction first. Hopefully we'll
> get that going for 4.7.
Pulled, thanks Will.
next prev parent reply other threads:[~2016-02-25 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 12:33 [GIT PULL] iommu/arm-smmu: Updates for 4.6 Will Deacon
2016-02-23 12:33 ` Will Deacon
[not found] ` <20160223123322.GL3966-5wv7dgnIgG8@public.gmane.org>
2016-02-25 15:00 ` Joerg Roedel [this message]
2016-02-25 15:00 ` Joerg Roedel
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=20160225150055.GC2280@suse.de \
--to=jroedel-l3a5bk7wagm@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.