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.11-rc1
Date: Tue, 28 Feb 2017 16:24:34 +0100 [thread overview]
Message-ID: <20170228152428.GA26932@8bytes.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1277 bytes --]
Hi Linus,
The following changes since commit 86292b33d4b79ee03e2f43ea0381ef85f077c760:
Merge branch 'akpm' (patches from Andrew) (2017-02-27 23:09:29 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fix-v4.11-rc0-2
for you to fetch changes up to b7a42b9d38063e58cdf201c575da75943f71051e:
iommu/amd: Fix crash when accessing AMD-Vi sysfs entries (2017-02-28 15:48:23 +0100)
----------------------------------------------------------------
IOMMU Fixes:
* Fix and issue introduced this merge window into the AMD and
Intel IOMMU drivers that causes an oops when the
vendor-specific sysfs-entries are accessed.
Reason for this issue is that I forgot to update the sysfs
code in the drivers when moving the iommu 'struct device' to
the iommu-core.
----------------------------------------------------------------
Joerg Roedel (2):
iommu/vt-d: Fix crash when accessing VT-d sysfs entries
iommu/amd: Fix crash when accessing AMD-Vi sysfs entries
drivers/iommu/amd_iommu_init.c | 4 ++--
drivers/iommu/amd_iommu_types.h | 5 +++++
drivers/iommu/intel-iommu.c | 17 +++++++++++------
3 files changed, 18 insertions(+), 8 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-02-28 15:24 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=20170228152428.GA26932@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