From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [git pull] IOMMU Fixes for Linux v3.16-rc2
Date: Tue, 24 Jun 2014 10:54:18 +0200 [thread overview]
Message-ID: <20140624085418.GB2782@8bytes.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1124 bytes --]
Hi Linus,
The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:
Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v3.16-rc1
for you to fetch changes up to d73a6d722a675dbba8f6b52c964a7076a24a12c1:
iommu/amd: Fix small race between invalidate_range_end/start (2014-06-20 16:14:22 +0200)
----------------------------------------------------------------
IOMMU Fixes for Linux v3.16-rc1
* Fix VT-d regression with handling multiple RMRR entries per
device
* Fix a small race that was left in the mmu_notifier handling in
the AMD IOMMUv2 driver
----------------------------------------------------------------
Jiang Liu (1):
iommu/vt-d: fix bug in handling multiple RMRRs for the same PCI device
Joerg Roedel (1):
iommu/amd: Fix small race between invalidate_range_end/start
drivers/iommu/amd_iommu_v2.c | 18 +++++++++++++-----
drivers/iommu/intel-iommu.c | 9 +++------
2 files changed, 16 insertions(+), 11 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2014-06-24 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 8:54 Joerg Roedel [this message]
[not found] ` <20140624085418.GB2782-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-06-28 2:03 ` [git pull] IOMMU Fixes for Linux v3.16-rc2 Linus Torvalds
[not found] ` <CAADWXX_TzcJQ3K07MsK1Ua6QqmTwDiqUM7aZYnZXWj9t9A_OmQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-30 7:40 ` 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=20140624085418.GB2782@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@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).