From: Ariel Otilibili <ariel.otilibili@6wind.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 1/1] pcapng: warn if NULL is passed to rte_pcapng_close
Date: Wed, 26 Feb 2025 16:09:27 +0100 [thread overview]
Message-ID: <CAF1zDgbyybza6r=O5Dh3JiosLDHHsO2m8qfKwd52mT7vVMXXeQ@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUCTKvqKFXGKtsgb8Fu1sk5s4UYzKMGw3YF-u1fq3fGOQw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
Hello Patrick,
On Tue, Feb 25, 2025 at 9:42 PM Patrick Robb <probb@iol.unh.edu> wrote:
> Recheck-request: iol-marvell-Functional
>
> Putting in a recheck as I believe the fail CI reported is false.
>
>>
>>
Thanks for the heads up. This patch did supersede version 2,
https://patches.dpdk.org/project/dpdk/patch/20250224164031.587829-2-ariel.otilibili@6wind.com/
Regards,
Ariel
[-- Attachment #2: Type: text/html, Size: 1080 bytes --]
next prev parent reply other threads:[~2025-02-26 15:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 16:08 [PATCH 0/1] pcapng: fix null dereference in rte_pcapng_close Ariel Otilibili
2025-02-16 16:08 ` [PATCH 1/1] " Ariel Otilibili
2025-02-16 16:51 ` Stephen Hemminger
2025-02-23 21:41 ` [PATCH v2 0/1] warn if NULL is passed to rte_pcapng_close Ariel Otilibili
2025-02-23 21:41 ` [PATCH v2 1/1] pcapng: " Ariel Otilibili
2025-02-23 22:04 ` Dmitry Kozlyuk
2025-02-24 15:42 ` Stephen Hemminger
2025-02-24 16:42 ` Ariel Otilibili
2025-02-25 20:39 ` Patrick Robb
2025-02-26 15:09 ` Ariel Otilibili [this message]
2025-02-24 16:40 ` [PATCH v3 0/1] pcapng: fix null dereference in rte_pcapng_close Ariel Otilibili
2025-02-24 16:40 ` [PATCH v3 1/1] " Ariel Otilibili
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='CAF1zDgbyybza6r=O5Dh3JiosLDHHsO2m8qfKwd52mT7vVMXXeQ@mail.gmail.com' \
--to=ariel.otilibili@6wind.com \
--cc=dev@dpdk.org \
--cc=probb@iol.unh.edu \
/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).