From: Vasant Hegde via iommu <iommu@lists.linux-foundation.org>
To: <joro@8bytes.org>, <iommu@lists.linux-foundation.org>
Cc: Vasant Hegde <vasant.hegde@amd.com>
Subject: [PATCH v2 0/5] iommu/amd: Cleanup and fixes
Date: Tue, 1 Mar 2022 14:26:21 +0530 [thread overview]
Message-ID: <20220301085626.87680-1-vasant.hegde@amd.com> (raw)
This series contains various cleanup and trivial fixes.
Changes in v2:
- Fixed error log message in patch 1 as suggested by Joerg.
Suravee Suthikulpanit (2):
iommu/amd: Improve error handling for amd_iommu_init_pci
iommu/amd: Improve amd_iommu_v2_exit()
Vasant Hegde (3):
iommu/amd: Call memunmap in error path
iommu/amd: Clean up function declarations
iommu/amd: Remove unused struct fault.devid
drivers/iommu/amd/amd_iommu.h | 4 ----
drivers/iommu/amd/init.c | 18 ++++++++++++++----
drivers/iommu/amd/iommu_v2.c | 35 +++++++++++++++++------------------
3 files changed, 31 insertions(+), 26 deletions(-)
--
2.27.0
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2022-03-01 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 8:56 Vasant Hegde via iommu [this message]
2022-03-01 8:56 ` [PATCH v2 1/5] iommu/amd: Improve error handling for amd_iommu_init_pci Vasant Hegde via iommu
2022-03-01 8:56 ` [PATCH v2 2/5] iommu/amd: Call memunmap in error path Vasant Hegde via iommu
2022-03-01 8:56 ` [PATCH v2 3/5] iommu/amd: Clean up function declarations Vasant Hegde via iommu
2022-03-01 8:56 ` [PATCH v2 4/5] iommu/amd: Remove unused struct fault.devid Vasant Hegde via iommu
2022-03-01 8:56 ` [PATCH v2 5/5] iommu/amd: Improve amd_iommu_v2_exit() Vasant Hegde via iommu
2022-03-04 9:39 ` [PATCH v2 0/5] iommu/amd: Cleanup and fixes Joerg Roedel
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=20220301085626.87680-1-vasant.hegde@amd.com \
--to=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=vasant.hegde@amd.com \
/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