From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: "joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org"
<joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: "iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [GIT PULL] iommu/arm-smmu: updates for 3.13
Date: Thu, 31 Oct 2013 00:59:02 +0000 [thread overview]
Message-ID: <20131031005902.GD28613@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20131009170238.GH8378-MRww78TxoiP5vMa5CHWGZ34zcgK1vI+I0E9HWUfgJXw@public.gmane.org>
On Wed, Oct 09, 2013 at 06:02:38PM +0100, Will Deacon wrote:
> Hi Joerg,
>
> Please pull these ARM SMMU updates for 3.13. The bulk of the changes are
> from Andreas, who has been having fun running the driver on real hardware. I
> expect some additional patches from him in the future to add support for
> things like device isolation once we've ironed out the wrinkles in the
> current proposals.
>
> I've successfully tested this lot in my modelled environments without any
> observed regressions.
Could you pull this please, Joerg? It would be good to have this in next
before the merge window...
Will
next prev parent reply other threads:[~2013-10-31 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 17:02 [GIT PULL] iommu/arm-smmu: updates for 3.13 Will Deacon
[not found] ` <20131009170238.GH8378-MRww78TxoiP5vMa5CHWGZ34zcgK1vI+I0E9HWUfgJXw@public.gmane.org>
2013-10-31 0:59 ` Will Deacon [this message]
[not found] ` <20131031005902.GD28613-MRww78TxoiP5vMa5CHWGZ34zcgK1vI+I0E9HWUfgJXw@public.gmane.org>
2013-11-01 11:31 ` joro-zLv9SwRftAIdnm+yROfE0A
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=20131031005902.GD28613@mudshark.cambridge.arm.com \
--to=will.deacon-5wv7dgnigg8@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@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).