From: Jason Gunthorpe <jgg@ziepe.ca>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux.dev, joro@8bytes.org, suravee.suthikulpanit@amd.com
Subject: Re: [PATCH 0/6] iommu/amd: Misc cleanup
Date: Tue, 6 Feb 2024 08:58:27 -0400 [thread overview]
Message-ID: <20240206125827.GE31743@ziepe.ca> (raw)
In-Reply-To: <20240118090105.5864-1-vasant.hegde@amd.com>
On Thu, Jan 18, 2024 at 09:00:59AM +0000, Vasant Hegde wrote:
> This patch series removes unused macros, redundant check and
> unncessary EXPORT_SYMBOLS. No major functional changes intended.
>
> Thanks,
> Vasant
>
> Vasant Hegde (6):
> iommu/amd: Remove unused PPR_* macros
> iommu/amd: Remove unused IOVA_* macro
> iommu/amd: Remove unused APERTURE_* macros
> iommu/amd: Remove duplicate function declarations from amd_iommu.h
> iommu/amd: Remove redundant error check in amd_iommu_probe_device()
> iommu/amd: Remove EXPORT_SYMBOL for perf counter related functions
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Jason
next prev parent reply other threads:[~2024-02-06 12:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 9:00 [PATCH 0/6] iommu/amd: Misc cleanup Vasant Hegde
2024-01-18 9:01 ` [PATCH 1/6] iommu/amd: Remove unused PPR_* macros Vasant Hegde
2024-01-18 9:01 ` [PATCH 2/6] iommu/amd: Remove unused IOVA_* macro Vasant Hegde
2024-01-18 9:01 ` [PATCH 3/6] iommu/amd: Remove unused APERTURE_* macros Vasant Hegde
2024-01-18 9:01 ` [PATCH 4/6] iommu/amd: Remove duplicate function declarations from amd_iommu.h Vasant Hegde
2024-01-18 9:01 ` [PATCH 5/6] iommu/amd: Remove redundant error check in amd_iommu_probe_device() Vasant Hegde
2024-01-18 9:01 ` [PATCH 6/6] iommu/amd: Remove EXPORT_SYMBOL for perf counter related functions Vasant Hegde
2024-01-19 19:37 ` [PATCH 0/6] iommu/amd: Misc cleanup Alejandro Jimenez
2024-01-22 3:49 ` Vasant Hegde
2024-02-06 12:58 ` Jason Gunthorpe [this message]
2024-02-09 10:41 ` 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=20240206125827.GE31743@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=suravee.suthikulpanit@amd.com \
--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