From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [git pull] IOMMU Fixes for Linux v5.2-rc4
Date: Fri, 14 Jun 2019 11:39:15 +0200 [thread overview]
Message-ID: <20190614093854.GA10155@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
Hi Linus,
The following changes since commit cd6c84d8f0cdc911df435bb075ba22ce3c605b07:
Linux 5.2-rc2 (2019-05-26 16:49:19 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v5.2-rc4
for you to fetch changes up to 4e4abae311e4b44aaf61f18a826fd7136037f199:
iommu/arm-smmu: Avoid constant zero in TLBI writes (2019-06-12 10:08:56 +0200)
----------------------------------------------------------------
IOMMU Fixes for Linux v5.2-rc4
Including:
- Three Fixes for Intel VT-d to fix a potential dead-lock, a
formatting fix and a bit setting fix.
- One fix for the ARM-SMMU to make it work on some platforms
with sub-optimal SMMU emulation.
----------------------------------------------------------------
Dave Jiang (1):
iommu/vt-d: Fix lock inversion between iommu->lock and device_domain_lock
Lu Baolu (2):
iommu: Add missing new line for dma type
iommu/vt-d: Set the right field for Page Walk Snoop
Robin Murphy (1):
iommu/arm-smmu: Avoid constant zero in TLBI writes
drivers/iommu/arm-smmu.c | 15 ++++++++++++---
drivers/iommu/intel-iommu.c | 7 ++++---
drivers/iommu/intel-pasid.c | 2 +-
drivers/iommu/iommu.c | 2 +-
4 files changed, 18 insertions(+), 8 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-06-14 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 9:39 Joerg Roedel [this message]
2019-06-14 16:15 ` [git pull] IOMMU Fixes for Linux v5.2-rc4 pr-tracker-bot
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=20190614093854.GA10155@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).