mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: baolu.lu@linux.intel.com, dwmw2@infradead.org, joro@8bytes.org,
	will@kernel.org, robin.murphy@arm.com, chao.p.peng@intel.com
Subject: Re: [PATCH v3 0/2] vtd: Minor cleanup
Date: Tue, 29 Oct 2024 12:42:48 +0800	[thread overview]
Message-ID: <2551f5b6-a1f3-4d4b-a17e-3451bdabfa90@linux.intel.com> (raw)
In-Reply-To: <20241024092146.715063-1-zhenzhong.duan@intel.com>

On 2024/10/24 17:21, Zhenzhong Duan wrote:
> Hi,
> 
> This cleanup the vtd dump code to dump lower entry after check current
> level entry's present bit. Also fix the print to avoid confusing.
> 
> See patch log for details.
> 
> Thanks
> Zhenzhong
> 
> Changelog:
> v3:
> - Fix a missed check
> - Refine commit log further
> 
> v2:
> - Add Fixes tag in patch1 (Baolu)
> - Refine commit log in patch2 (Baolu)
> 
> 
> Zhenzhong Duan (2):
>    iommu/vt-d: Fix checks and print in dmar_fault_dump_ptes()
>    iommu/vt-d: Fix checks and print in pgtable_walk()
> 
>   drivers/iommu/intel/iommu.c | 40 ++++++++++++++++++++++++-------------
>   1 file changed, 26 insertions(+), 14 deletions(-)

Queued for v6.13. Thank you!

--
baolu

      parent reply	other threads:[~2024-10-29  4:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24  9:21 Zhenzhong Duan
2024-10-24  9:21 ` [PATCH v3 1/2] iommu/vt-d: Fix checks and print in dmar_fault_dump_ptes() Zhenzhong Duan
2024-10-24  9:21 ` [PATCH v3 2/2] iommu/vt-d: Fix checks and print in pgtable_walk() Zhenzhong Duan
2024-10-29  4:42 ` Baolu Lu [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=2551f5b6-a1f3-4d4b-a17e-3451bdabfa90@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=chao.p.peng@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    --cc=zhenzhong.duan@intel.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®