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 v3.6-rc1
Date: Tue, 7 Aug 2012 16:44:30 +0200	[thread overview]
Message-ID: <20120807144430.GA8827@8bytes.org> (raw)


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

Hi Linus,

The following changes since commit 0d7614f09c1ebdbaa1599a5aba7593f147bf96ee:

  Linux 3.6-rc1 (2012-08-02 16:38:10 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v3.6-rc1

for you to fetch changes up to 31fe943599b7e5870edb9decb7fbb9538b218f26:

  iommu/amd: Fix ACS path checking (2012-08-06 18:10:04 +0200)

----------------------------------------------------------------
IOMMU fixes for Linux v3.6-rc1

These patches fix a couple of issues. First of all a few problems with
ACS on x86 introduced in the last merge window, where ACS did not work
on AMD and a NULL pointer dereference when there ran against SR-IOV
devices.
The patches fallen out of coccinelle checks fix a possible invalid
memory reference and a possible memory leak. The other patches mostly
fix build errors and warnings and a wrong return value.

----------------------------------------------------------------
Alex Williamson (2):
      iommu/intel: Fix ACS path checking
      iommu/amd: Fix ACS path checking

Hiroshi Doyu (2):
      iommu/tegra: smmu: Cleanup with lesser nest
      iommu/tegra: smmu: Fix error initial value at domain_init

Joerg Roedel (2):
      iommu: Add missing forward declaration in include file
      iommu/amd: Fix pci_request_acs() call-place

Julia Lawall (2):
      iommu/tegra: remove invalid reference to list iterator variable
      iommu/intel: add missing free_domain_mem

Sachin Kamat (1):
      iommu/exynos: Fix build error

Thierry Reding (1):
      iommu: Include linux/types.h

 drivers/iommu/amd_iommu.c      |   25 ++++++++++++++++++++++---
 drivers/iommu/amd_iommu_init.c |    6 +++---
 drivers/iommu/exynos-iommu.c   |    6 +++---
 drivers/iommu/intel-iommu.c    |   26 +++++++++++++++++++++++---
 drivers/iommu/tegra-smmu.c     |   17 ++++++++++-------
 include/linux/iommu.h          |    2 ++
 6 files changed, 63 insertions(+), 19 deletions(-)

Please pull.

Regards,

	Joerg


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

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

_______________________________________________
iommu mailing list
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

                 reply	other threads:[~2012-08-07 14:44 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=20120807144430.GA8827@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).