From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Cc: a.motakis-lrHrjnjw1UfHK3s98zE1ajGjJy/sRE9J@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [GIT PULL] iommu/arm-smmu: updates for 3.19
Date: Fri, 21 Nov 2014 12:30:58 +0100 [thread overview]
Message-ID: <20141121113058.GF3762@8bytes.org> (raw)
In-Reply-To: <20141119190006.GL15985-5wv7dgnIgG8@public.gmane.org>
On Wed, Nov 19, 2014 at 07:00:06PM +0000, Will Deacon wrote:
> Please can you pull these ARM SMMU changes for 3.19? As well as the
> usual driver updates (enabling support for the new NESTING attribute),
> there are also the IOMMU_NOEXEC patches from Antonios, which includes
> a fix for a resulting compiler warning in the AMD IOMMU driver.
Pulled, thanks Will.
WARNING: multiple messages have this Message-ID (diff)
From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] iommu/arm-smmu: updates for 3.19
Date: Fri, 21 Nov 2014 12:30:58 +0100 [thread overview]
Message-ID: <20141121113058.GF3762@8bytes.org> (raw)
In-Reply-To: <20141119190006.GL15985@arm.com>
On Wed, Nov 19, 2014 at 07:00:06PM +0000, Will Deacon wrote:
> Please can you pull these ARM SMMU changes for 3.19? As well as the
> usual driver updates (enabling support for the new NESTING attribute),
> there are also the IOMMU_NOEXEC patches from Antonios, which includes
> a fix for a resulting compiler warning in the AMD IOMMU driver.
Pulled, thanks Will.
next prev parent reply other threads:[~2014-11-21 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 19:00 [GIT PULL] iommu/arm-smmu: updates for 3.19 Will Deacon
2014-11-19 19:00 ` Will Deacon
[not found] ` <20141119190006.GL15985-5wv7dgnIgG8@public.gmane.org>
2014-11-21 11:30 ` Joerg Roedel [this message]
2014-11-21 11:30 ` 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=20141121113058.GF3762@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=a.motakis-lrHrjnjw1UfHK3s98zE1ajGjJy/sRE9J@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=treding-DDmLM1+adcrQT0dZR+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 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.