From: Patrick Robb <probb@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, thomas@monjalon.net,
Robin Jarry <rjarry@redhat.com>,
Aaron Conole <aconole@redhat.com>,
Michael Santana <maicolgabriel@hotmail.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Chengwen Feng <fengchengwen@huawei.com>
Subject: Re: [PATCH] ci: fix unit tests with Fedora 37
Date: Fri, 18 Oct 2024 10:04:39 -0400 [thread overview]
Message-ID: <CAJvnSUCeU_NUgxp8+3iQ9qD5xmtJj+iqFXeqP_u5XJXn14GG-Q@mail.gmail.com> (raw)
In-Reply-To: <20241018135641.3546518-1-david.marchand@redhat.com>
Acked-by: Patrick Robb <probb@iol.unh.edu>
next prev parent reply other threads:[~2024-10-18 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 13:56 David Marchand
2024-10-18 14:04 ` Patrick Robb [this message]
2024-10-18 16:07 ` David Marchand
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=CAJvnSUCeU_NUgxp8+3iQ9qD5xmtJj+iqFXeqP_u5XJXn14GG-Q@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=maicolgabriel@hotmail.com \
--cc=rjarry@redhat.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).