mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Suthikulpanit, Suravee" <suravee.suthikulpanit@amd.com>
To: Yu Zhang <zhangyu1@linux.microsoft.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
	joro@8bytes.org, jon.grimm@amd.com, vasant.hegde@amd.com,
	frank.gorishek@amd.com, thomas.lendacky@amd.com,
	santosh.shukla@amd.com, jacob.pan@linux.microsoft.com
Subject: Re: [PATCH 1/4] iommu/amd: Drop unused global exclusion range fields and init
Date: Fri, 24 Apr 2026 16:22:55 +0700	[thread overview]
Message-ID: <32db5a5d-1f81-432f-829b-3bdd480711cf@amd.com> (raw)
In-Reply-To: <fj6hhycko3nsxq7w3oj7mbnsa4ttmd5c7xcnjkcqmv4qyrednr@qbsiizpo4dma>



On 4/22/2026 4:03 PM, Yu Zhang wrote:
> This patch overlaps with mine [1], which was sent on March 31st with
> you on Cc. Jacob has reviewed it.
> 
> While I was still waiting on your comments, I realized your series
> goes beyond the dead code removal. So I believe I do not need to follow
> up on mine.
> 
> [1]https://lore.kernel.org/all/20260331152550.479841-1- 
> zhangyu1@linux.microsoft.com/
> 
> Thanks,
> Yu

Sorry  I missed that one. I will follow up with that thread. I am 
sending out v2, and will rebase my series on top of yours.

Thanks,
Suravee


  reply	other threads:[~2026-04-24  9:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20 17:00 [PATCH 0/4] iommu/amd: IVMD handling cleanup and ivmd= boot override Suravee Suthikulpanit
2026-04-20 17:00 ` [PATCH 1/4] iommu/amd: Drop unused global exclusion range fields and init Suravee Suthikulpanit
2026-04-22  9:03   ` Yu Zhang
2026-04-24  9:22     ` Suthikulpanit, Suravee [this message]
2026-04-20 17:00 ` [PATCH 2/4] iommu/amd: Do not convert IVMD exclusion range to unity range Suravee Suthikulpanit
2026-04-20 17:00 ` [PATCH 3/4] iommu/amd: Clean up and simplify IVMD entry handling Suravee Suthikulpanit
2026-04-20 17:00 ` [PATCH 4/4] iommu/amd: Introduce boot option ivmd=seg:bus:dev.fun,start,size,flags Suravee Suthikulpanit
2026-04-22 10:56   ` Yu Zhang
2026-04-23  8:08     ` Suthikulpanit, Suravee

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=32db5a5d-1f81-432f-829b-3bdd480711cf@amd.com \
    --to=suravee.suthikulpanit@amd.com \
    --cc=frank.gorishek@amd.com \
    --cc=iommu@lists.linux.dev \
    --cc=jacob.pan@linux.microsoft.com \
    --cc=jon.grimm@amd.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=santosh.shukla@amd.com \
    --cc=thomas.lendacky@amd.com \
    --cc=vasant.hegde@amd.com \
    --cc=zhangyu1@linux.microsoft.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
all inboxes | Powered by JetHome®