From: Joerg Roedel <joro@8bytes.org>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux-foundation.org
Subject: Re: [PATCH 0/5] iommu/amd: Cleanup and fixes
Date: Mon, 28 Feb 2022 13:48:00 +0100 [thread overview]
Message-ID: <YhzEgGNJukt9IKm2@8bytes.org> (raw)
In-Reply-To: <20220221045916.19701-1-vasant.hegde@amd.com>
On Mon, Feb 21, 2022 at 10:29:11AM +0530, Vasant Hegde wrote:
> This series contains various cleanup and trivial fixes.
>
> 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 | 16 ++++++++++++----
> drivers/iommu/amd/iommu_v2.c | 35 +++++++++++++++++------------------
> 3 files changed, 29 insertions(+), 26 deletions(-)
Besides the error messages in the first patch this looks good to me.
Please re-send with the updates and I consider it for v5.18.
Thanks,
Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2022-02-28 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 4:59 [PATCH 0/5] iommu/amd: Cleanup and fixes Vasant Hegde via iommu
2022-02-21 4:59 ` [PATCH 1/5] iommu/amd: Improve error handling for amd_iommu_init_pci Vasant Hegde via iommu
2022-02-28 12:47 ` Joerg Roedel
2022-03-01 8:58 ` Vasant Hegde via iommu
2022-02-21 4:59 ` [PATCH 2/5] iommu/amd: Call memunmap in error path Vasant Hegde via iommu
2022-02-21 4:59 ` [PATCH 3/5] iommu/amd: Clean up function declarations Vasant Hegde via iommu
2022-02-21 4:59 ` [PATCH 4/5] iommu/amd: Remove unused struct fault.devid Vasant Hegde via iommu
2022-02-21 4:59 ` [PATCH 5/5] iommu/amd: Improve amd_iommu_v2_exit() Vasant Hegde via iommu
2022-02-28 12:48 ` Joerg Roedel [this message]
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=YhzEgGNJukt9IKm2@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.