From: Joerg Roedel <joro@8bytes.org>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux-foundation.org
Subject: Re: [PATCH v2 0/5] iommu/amd: Cleanup and fixes
Date: Fri, 4 Mar 2022 10:39:44 +0100 [thread overview]
Message-ID: <YiHeYH3zWAQ86jmo@8bytes.org> (raw)
In-Reply-To: <20220301085626.87680-1-vasant.hegde@amd.com>
On Tue, Mar 01, 2022 at 02:26:21PM +0530, Vasant Hegde wrote:
> 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
Applied, thanks Vasant and Suravee.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2022-03-04 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 8:56 [PATCH v2 0/5] iommu/amd: Cleanup and fixes Vasant Hegde via iommu
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 ` 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=YiHeYH3zWAQ86jmo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox