qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Zhenzhong Duan <zhenzhong.duan@intel.com>,
	qemu-devel@nongnu.org, alex.williamson@redhat.com,
	eric.auger@redhat.com, mst@redhat.com, jasowang@redhat.com,
	peterx@redhat.com, ddutile@redhat.com, nicolinc@nvidia.com,
	shameerali.kolothum.thodi@huawei.com, joao.m.martins@oracle.com,
	clement.mathieu--drif@eviden.com, kevin.tian@intel.com,
	yi.l.liu@intel.com, chao.p.peng@intel.com
Subject: Re: [PATCH v3 0/4] VFIO and IOMMU prerequisite stuff for IOMMU nesting support
Date: Wed, 4 Jun 2025 14:20:23 +0200	[thread overview]
Message-ID: <c34c79ce-6e3e-44b8-8293-714aa783a837@redhat.com> (raw)
In-Reply-To: <20250604120820.GA5028@nvidia.com>

On 6/4/25 14:08, Jason Gunthorpe wrote:
> On Wed, Jun 04, 2025 at 08:59:37AM +0200, Cédric Le Goater wrote:
> 
>> b4 complained for a couple of trailers :
> 
> He re-reviewed patches he contributed to making :)
> 
>>      Reviewed-by: Nicolin Chen <nicolinc@nvidia.com> (✗ DKIM/nvidia.com)
> 
> But why do you have an X? The messages are properly formed leaving the
> nvidia server, I checked.. And my b4 is happy:
> 
> $ b4 am https://lore.kernel.org/qemu-devel/aBUHLWY1Qdapgl+Y@Asurada-Nvidia/
> Grabbing thread from lore.kernel.org/all/aBUHLWY1Qdapgl%2BY@Asurada-Nvidia/t.mbox.gz
> Analyzing 50 messages in the thread
> Looking for additional code-review trailers on lore.kernel.org
> Analyzing 7 code-review messages
> Checking attestation on all messages, may take a moment...
> ---
>    [PATCH v2 1/6] hw/arm/smmuv3: Add support to associate a PCIe RC
>      + Reviewed-by: Nicolin Chen <nicolinc@nvidia.com> (✓ DKIM/nvidia.com)
>    [PATCH v2 2/6] hw/arm/virt-acpi-build: Update IORT for multiple smmuv3 devices
>      + Reviewed-by: Nicolin Chen <nicolinc@nvidia.com> (✓ DKIM/nvidia.com)
>    [PATCH v2 3/6] hw/arm/virt: Factor out common SMMUV3 dt bindings code
>      + Reviewed-by: Nicolin Chen <nicolinc@nvidia.com> (✓ DKIM/nvidia.com)
>      + Reviewed-by: Eric Auger <eric.auger@redhat.com> (✓ DKIM/redhat.com)
>    [PATCH v2 4/6] hw/arm/virt: Add an SMMU_IO_LEN macro
>      + Reviewed-by: Eric Auger <eric.auger@redhat.com> (✓ DKIM/redhat.com)
>      + Reviewed-by: Donald Dutile <ddutile@redhat.com> (✓ DKIM/redhat.com)
>    [PATCH v2 5/6] hw/arm/virt: Add support for smmuv3 device
>    [PATCH v2 6/6] hw/arm/smmuv3: Enable smmuv3 device creation
>      + Reviewed-by: Nicolin Chen <nicolinc@nvidia.com> (✓ DKIM/nvidia.com)

Ah ! Interesting, using the link doesn't report issues.

I use the message-id on v3 :

$ b4 am 20250604062115.4004200-1-zhenzhong.duan@intel.com
Analyzing 7 messages in the thread
Analyzing 76 code-review messages
Checking attestation on all messages, may take a moment...
---
   ✓ [PATCH v3 1/4] backends/iommufd: Add a helper to invalidate user-managed HWPT
   ✓ [PATCH v3 2/4] vfio/iommufd: Add properties and handlers to TYPE_HOST_IOMMU_DEVICE_IOMMUFD
   ✓ [PATCH v3 3/4] vfio/iommufd: Implement [at|de]tach_hwpt handlers
   ✓ [PATCH v3 4/4] vfio/iommufd: Save vendor specific device info
   ---
   ✓ Signed: DKIM/intel.com
---
Total patches: 4
---
NOTE: some trailers ignored due to from/email mismatches:
     ! Trailer: Reviewed-by: Nicolin Chen <nicolinc@nvidia.com>
      Msg From: Nicolin Chen via <qemu-devel@nongnu.org>
     ! Trailer: Reviewed-by: Nicolin Chen <nicolinc@nvidia.com>
      Msg From: Cédric Le Goater <clg@redhat.com>
NOTE: Rerun with -S to apply them anyway
---
Cover: ./v3_20250604_zhenzhong_duan_vfio_and_iommu_prerequisite_stuff_for_iommu_nesting_support.cover
  Link: https://lore.kernel.org/r/20250604062115.4004200-1-zhenzhong.duan@intel.com
  Base: not specified
        git am ./v3_20250604_zhenzhong_duan_vfio_and_iommu_prerequisite_stuff_for_iommu_nesting_support.mbx



C.



  reply	other threads:[~2025-06-04 12:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04  6:21 [PATCH v3 0/4] VFIO and IOMMU prerequisite stuff for IOMMU nesting support Zhenzhong Duan
2025-06-04  6:21 ` [PATCH v3 1/4] backends/iommufd: Add a helper to invalidate user-managed HWPT Zhenzhong Duan
2025-06-04  6:21 ` [PATCH v3 2/4] vfio/iommufd: Add properties and handlers to TYPE_HOST_IOMMU_DEVICE_IOMMUFD Zhenzhong Duan
2025-06-04  6:21 ` [PATCH v3 3/4] vfio/iommufd: Implement [at|de]tach_hwpt handlers Zhenzhong Duan
2025-06-04  6:21 ` [PATCH v3 4/4] vfio/iommufd: Save vendor specific device info Zhenzhong Duan
2025-06-04  6:59 ` [PATCH v3 0/4] VFIO and IOMMU prerequisite stuff for IOMMU nesting support Cédric Le Goater
2025-06-04 12:08   ` Jason Gunthorpe
2025-06-04 12:20     ` Cédric Le Goater [this message]
2025-06-04 12:28       ` Jason Gunthorpe

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=c34c79ce-6e3e-44b8-8293-714aa783a837@redhat.com \
    --to=clg@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=chao.p.peng@intel.com \
    --cc=clement.mathieu--drif@eviden.com \
    --cc=ddutile@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=joao.m.martins@oracle.com \
    --cc=kevin.tian@intel.com \
    --cc=mst@redhat.com \
    --cc=nicolinc@nvidia.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=yi.l.liu@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).