Linux IOMMU Development
 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.1-rc3
Date: Mon, 11 May 2015 19:52:55 +0200	[thread overview]
Message-ID: <20150511175255.GA31276@8bytes.org> (raw)


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

Hi Linus,

The following changes since commit 5ebe6afaf0057ac3eaeb98defd5456894b446d22:

  Linux 4.1-rc2 (2015-05-03 19:22:23 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.1-rc3

for you to fetch changes up to 5dc5616ee850eaba055bb469a6c4a471d489140e:

  iommu/arm-smmu: Fix sign-extension of upstream bus addresses at stage 1 (2015-05-11 18:36:20 +0200)

----------------------------------------------------------------
IOMMU Fixes for Linux v4.1-rc3

Three fixes have queued up:

        * Reference count fix in the AMD IOMMUv2 driver

        * Sign extension fix in the ARM-SMMU driver

	* Build fix for rockchip driver with device tree

----------------------------------------------------------------
Arnd Bergmann (1):
      iommu/rockchip: Fix build without CONFIG_OF

Oded Gabbay (1):
      iommu/amd: Fix bug in put_pasid_state_wait

Will Deacon (1):
      iommu/arm-smmu: Fix sign-extension of upstream bus addresses at stage 1

 drivers/iommu/amd_iommu_v2.c   |  1 +
 drivers/iommu/arm-smmu.c       | 30 ++----------------------------
 drivers/iommu/rockchip-iommu.c |  4 +---
 3 files changed, 4 insertions(+), 31 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 --]



                 reply	other threads:[~2015-05-11 17:52 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=20150511175255.GA31276@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