iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
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 v4.12-rc1
Date: Fri, 19 May 2017 11:32:24 +0200	[thread overview]
Message-ID: <20170519093218.GA6658@8bytes.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1262 bytes --]

Hi Linus,

The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:

  Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.12-rc1

for you to fetch changes up to 745b6e74704782488dd875292bc49e24d23e81fd:

  iommu/mediatek: Include linux/dma-mapping.h (2017-05-17 14:51:54 +0200)

----------------------------------------------------------------
IOMMU Fixes for Linux v4.12-rc1

Including:

	* Another compile-fix as a fallout of the recent header-file
	  cleanup

	* Add a missing IO/TLB flush to the Intel VT-d kdump code path

	* A fix for ARM64 dma code to only access initialized
	  iova_domain members

----------------------------------------------------------------
Arnd Bergmann (1):
      iommu/mediatek: Include linux/dma-mapping.h

KarimAllah Ahmed (1):
      iommu/vt-d: Flush the IOTLB to get rid of the initial kdump mappings

Robin Murphy (1):
      iommu/dma: Don't touch invalid iova_domain members

 drivers/iommu/dma-iommu.c    | 13 ++++++++-----
 drivers/iommu/intel-iommu.c  |  5 ++++-
 drivers/iommu/mtk_iommu_v1.c |  1 +
 3 files changed, 13 insertions(+), 6 deletions(-)

Please pull.

Thanks,

	Joerg

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



                 reply	other threads:[~2017-05-19  9:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170519093218.GA6658@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).