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.9-rc4
Date: Wed, 27 Mar 2013 10:46:35 +0100 [thread overview]
Message-ID: <20130327094547.GA8513@8bytes.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1507 bytes --]
Hi Linus,
The following changes since commit 6dbe51c251a327e012439c4772097a13df43c5b8:
Linux 3.9-rc1 (2013-03-03 15:11:05 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v3.9-rc4
for you to fetch changes up to c2a2876e863356b092967ea62bebdb4dd663af80:
iommu/amd: Make sure dma_ops are set for hotplug devices (2013-03-27 09:59:50 +0100)
----------------------------------------------------------------
IOMMU fixes for Linux v3.9-rc4
Here are some fixes which have collected since Linux v3.9-rc1. The most
important one fixes a long-standing regressen which make re-hotplugged
devices unusable when AMD IOMMU is used. The other patches fix build
issues (build regression on OMAP and a section mismatch). One patch just
removes a duplicate header include.
----------------------------------------------------------------
Arnd Bergmann (1):
iommu: OMAP: build only on OMAP2+
Joerg Roedel (1):
iommu/amd: Make sure dma_ops are set for hotplug devices
Nikola Pajkovsky (1):
amd_iommu_init: remove __init from amd_iommu_erratum_746_workaround
Wei Yongjun (1):
x86, io_apic: remove duplicated include from irq_remapping.c
drivers/iommu/Kconfig | 2 +-
drivers/iommu/amd_iommu.c | 22 ++++++++++------------
drivers/iommu/amd_iommu_init.c | 2 +-
drivers/iommu/irq_remapping.c | 1 -
4 files changed, 12 insertions(+), 15 deletions(-)
Please pull.
Regards,
Joerg
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2013-03-27 9:46 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=20130327094547.GA8513@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).