From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [git pull] IOMMU Fixes for Linux v5.4-rc5
Date: Wed, 30 Oct 2019 14:02:57 +0100 [thread overview]
Message-ID: <20191030130251.GA11315@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
Hi Linus,
The following changes since commit d6d5df1db6e9d7f8f76d2911707f7d5877251b02:
Linux 5.4-rc5 (2019-10-27 13:19:19 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v5.4-rc5
for you to fetch changes up to 160c63f909ffbc797c0bbe23310ac1eaf2349d2f:
iommu/vt-d: Fix panic after kexec -p for kdump (2019-10-30 10:30:22 +0100)
----------------------------------------------------------------
IOMMU Fixes for Linux v5.4-rc5
Including:
- Follow-on fix for Renesas IPMMU to get rid of a redundant
error message.
- Quirk for AMD IOMMU to make it work on another Acer Laptop
model with a broken IVRS ACPI table.
- Fix for a panic at kdump in the Intel IOMMU driver.
----------------------------------------------------------------
John Donnelly (1):
iommu/vt-d: Fix panic after kexec -p for kdump
Takashi Iwai (1):
iommu/amd: Apply the same IVRS IOAPIC workaround to Acer Aspire A315-41
YueHaibing (1):
iommu/ipmmu-vmsa: Remove dev_err() on platform_get_irq() failure
drivers/iommu/amd_iommu_quirks.c | 13 +++++++++++++
drivers/iommu/intel-iommu.c | 2 +-
drivers/iommu/ipmmu-vmsa.c | 4 +---
3 files changed, 15 insertions(+), 4 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-10-30 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 13:02 Joerg Roedel [this message]
2019-10-30 13:25 ` [git pull] IOMMU Fixes for Linux v5.4-rc5 pr-tracker-bot
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=20191030130251.GA11315@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).