From: alex.williamson@redhat.com (Alex Williamson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] iommu: arm/smmu: fixes for 3.13
Date: Fri, 06 Dec 2013 14:47:35 -0700 [thread overview]
Message-ID: <1386366455.25738.511.camel@ul30vt.home> (raw)
In-Reply-To: <20131206175319.GD8853@mudshark.cambridge.arm.com>
On Fri, 2013-12-06 at 17:53 +0000, Will Deacon wrote:
> Hi Alex (CC'ing Joerg),
>
> Please can you pull the following fixes to the arm/smmu driver for 3.13?
Hi Will,
I'll use my vfio tree since it's already included in next. I've pulled
to here:
git://github.com/awilliam/linux-vfio.git for-linus
Unless something explodes I'll forward it on next week. Thanks,
Alex
> --->8
>
> The following changes since commit dc1ccc48159d63eca5089e507c82c7d22ef60839:
>
> Linux 3.13-rc2 (2013-11-29 12:57:14 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git for-joerg/arm-smmu/fixes
>
> for you to fetch changes up to 89a23cde75a7f0b3d8b0c156964eca0c23d2f1eb:
>
> iommu/arm-smmu: fix error return code in arm_smmu_device_dt_probe() (2013-12-06 16:44:25 +0000)
>
> ----------------------------------------------------------------
> Wei Yongjun (1):
> iommu/arm-smmu: fix error return code in arm_smmu_device_dt_probe()
>
> Will Deacon (2):
> iommu/arm-smmu: use mutex instead of spinlock for locking page tables
> iommu/arm-smmu: remove potential NULL dereference on mapping path
>
> drivers/iommu/arm-smmu.c | 66 ++++++++++++++++++++----------------------------
> 1 file changed, 28 insertions(+), 38 deletions(-)
prev parent reply other threads:[~2013-12-06 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 17:53 [GIT PULL] iommu: arm/smmu: fixes for 3.13 Will Deacon
2013-12-06 21:47 ` Alex Williamson [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=1386366455.25738.511.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).