DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Shani Peretz <shperetz@nvidia.com>, dev@dpdk.org
Subject: Re: [PATCH] eal: fix DMA mask validation inconsistency in IOVA VA
Date: Thu, 18 Sep 2025 16:59:36 -0400	[thread overview]
Message-ID: <CAJvnSUD77gw1f0ECo5XuSJrUNWkuJksohQ3hfFNr09j1DP2tLA@mail.gmail.com> (raw)
In-Reply-To: <3107280.irdbgypaU6@thomas>

[-- Attachment #1: Type: text/plain, Size: 775 bytes --]

Hi Thomas,

FYI the recheck you submitted is for Shani's v1 patch. The recheck pipeline
picked up your request and is not running a recheck because the patch state
is superseded (which blocks the recheck). If you still want a recheck on
the v1, I will just remove the line in our script which stops the recheck
is the series is superseded.

It looks like Shani submitted a v2 this morning and all tests are passing:
https://patchwork.dpdk.org/project/dpdk/patch/20250918064754.6116-1-shperetz@nvidia.com/


On Wed, Sep 17, 2025 at 4:49 AM Thomas Monjalon <thomas@monjalon.net> wrote:

> Recheck-request: rebase=main, iol-mellanox-Functional,
> iol-compile-amd64-testing, iol-compile-arm64-testing,
> iol-unit-amd64-testing, iol-unit-arm64-testing
>
>
>

[-- Attachment #2: Type: text/html, Size: 1220 bytes --]

  reply	other threads:[~2025-09-18 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-08 16:34 Shani Peretz
2025-09-09 10:17 ` Burakov, Anatoly
2025-09-16 13:15 ` Patrick Robb
2025-09-17  8:49 ` Thomas Monjalon
2025-09-18 20:59   ` Patrick Robb [this message]
2025-09-18  6:47 ` [PATCH v2] " Shani Peretz
2025-09-18  7:55   ` Shani Peretz

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=CAJvnSUD77gw1f0ECo5XuSJrUNWkuJksohQ3hfFNr09j1DP2tLA@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=dev@dpdk.org \
    --cc=shperetz@nvidia.com \
    --cc=thomas@monjalon.net \
    /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).