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.5-rc5
Date: Sun, 12 Jan 2020 10:59:41 +0100 [thread overview]
Message-ID: <20200112095936.GA17108@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
Hi Linus,
The following changes since commit c79f46a282390e0f5b306007bf7b11a46d529538:
Linux 5.5-rc5 (2020-01-05 14:23:27 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git iommu-fixes-v5.5-rc5
for you to fetch changes up to 55817b340a31951d23d1692db45522560b1d20f9:
iommu/dma: fix variable 'cookie' set but not used (2020-01-07 17:08:58 +0100)
----------------------------------------------------------------
IOMMU Fixes for Linux v5.5-rc5
Including:
- Two fixes for VT-d and generic IOMMU code to fix teardown on
error handling code paths.
- Patch for the Intel VT-d driver to fix handling of non-PCI
devices
- Fix W=1 compile warning in dma-iommu code
----------------------------------------------------------------
Jon Derrick (2):
iommu: Remove device link to group on failure
iommu/vt-d: Unlink device if failed to add to group
Patrick Steinhardt (1):
iommu/vt-d: Fix adding non-PCI devices to Intel IOMMU
Qian Cai (1):
iommu/dma: fix variable 'cookie' set but not used
drivers/iommu/dma-iommu.c | 3 ---
drivers/iommu/intel-iommu.c | 22 ++++++++++++++++++----
drivers/iommu/iommu.c | 1 +
3 files changed, 19 insertions(+), 7 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-01-12 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 9:59 Joerg Roedel [this message]
2020-01-12 17:40 ` [git pull] IOMMU Fixes for Linux v5.5-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=20200112095936.GA17108@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