From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: "stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"benjamin.walker@intel.com" <benjamin.walker@intel.com>,
Ian Stokes <ian.stokes@intel.com>,
John McNamara <john.mcnamara@intel.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
"pingx.yu@intel.com" <pingx.yu@intel.com>,
"qian.q.xu@intel.com" <qian.q.xu@intel.com>,
"yuan.peng@intel.com" <yuan.peng@intel.com>,
"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>,
"Jiang, YuX" <yux.jiang@intel.com>
Subject: Re: 19.11.11 (RC2) patches review and test
Date: Tue, 4 Jan 2022 11:34:14 +0100 [thread overview]
Message-ID: <CAATJJ0LqK1u0M64HTcOwG1PG4-Rg6-LWa=D4__8FjJDat5FsLQ@mail.gmail.com> (raw)
In-Reply-To: <DM4PR12MB51674A5CDF47CC871E96179DDA459@DM4PR12MB5167.namprd12.prod.outlook.com>
Done my own testing as well, for the logs;
Canonical(R) Testing
* Build tests of DPDK & OVS 2.13.3 on Ubuntu 20.04 (meson based)
* Functional and performance tests based on OVS-DPDK on x86_64
* Autopkgtests for DPDK and OpenvSwitch
The former other use case of 19.11 was Ubuntu 20.10 but that no longer
is an active release and therefore skipped.
Checking past verification logs I have all the usual suspects for
19.11.11 completed, except one.
We are missing "[Intel(R) Testing with Open vSwitch]"
As these threads grew out of control chances are quite high that
someone submitted it but I fail to see/find it.
I even have the feeling I already asked this and got a positive
response, but I fail to find something referrable like a mailing list
link.
So please bear with me and send me a link to the dpdk mailing list
archive entry that you stated your tests as done.
prev parent reply other threads:[~2022-01-04 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 7:59 christian.ehrhardt
2021-12-30 13:47 ` Ali Alnubani
2022-01-04 10:34 ` Christian Ehrhardt [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='CAATJJ0LqK1u0M64HTcOwG1PG4-Rg6-LWa=D4__8FjJDat5FsLQ@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ian.stokes@intel.com \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=pezhang@redhat.com \
--cc=pingx.yu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=stable@dpdk.org \
--cc=yuan.peng@intel.com \
--cc=yux.jiang@intel.com \
--cc=zhaoyan.chen@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).