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.6-rc3
Date: Fri, 22 Apr 2016 11:56:18 +0200	[thread overview]
Message-ID: <20160422095609.GA18272@8bytes.org> (raw)


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

Hi Linus,

The following changes since commit bf16200689118d19de1b8d2a3c314fc21f5dc7bb:

  Linux 4.6-rc3 (2016-04-10 17:58:30 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.6-rc4

for you to fetch changes up to 9800699c645952da6a7399194d3e762b84cde3cd:

  iommu/arm-smmu: Don't allocate resources for bypass domains (2016-04-21 16:47:32 +0200)

----------------------------------------------------------------
IOMMU Fixes for Linux v4.6-rc4

The fixes include:

	* Two patches to revert the use of default domains in the ARM
	  SMMU driver. Enabling this caused regressions which need more
	  thorough fixing. So the regressions are fixed for now by
	  disabling the use of default domains.

	* A fix for a v4.4 regression in the AMD IOMMU driver which
	  broke devices behind invisible PCIe-to-PCI bridges with IOMMU
	  enabled.

----------------------------------------------------------------
Joerg Roedel (1):
      iommu/amd: Fix checking of pci dma aliases

Robin Murphy (1):
      iommu/arm-smmu: Don't allocate resources for bypass domains

Will Deacon (1):
      iommu/arm-smmu: Fix stream-match conflict with IOMMU_DOMAIN_DMA

 drivers/iommu/amd_iommu.c | 87 +++++++++++++++++++++++++++++++++++++++++------
 drivers/iommu/arm-smmu.c  | 22 ++++++++----
 2 files changed, 91 insertions(+), 18 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:[~2016-04-22  9:56 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=20160422095609.GA18272@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).