From: Nathan Southern <nsouthern@linuxfoundation.org>
To: dev@dpdk.org, "Aaron Conole" <aconole@redhat.com>,
ahassick@iol.unh.edu, alialnu@mellanox.com,
"Tammie Williams" <aweltz@linuxfoundation.org>,
blo@iol.unh.edu, bluca@debian.org, "Richardson,
Bruce" <bruce.richardson@intel.com>,
chun.zhang@intel.com, ci@dpdk.org,
"David Marchand" <david.marchand@redhat.com>,
erezsc@mellanox.com, erezsc@nvidia.com, ferruh.yigit@intel.com,
galco@mellanox.com, "Gal Cohen (ProdM)" <galco@nvidia.com>,
georgii.tkachuk@intel.com, gurucode@gmail.com,
hemant.agrawal@nxp.com, hnadeau@iol.unh.edu,
"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
ian.stokes@intel.com,
"Jerin Jacob Kollanukkaran" <jerinj@marvell.com>,
jerinjacobk@gmail.com, "Mcnamara, John" <john.mcnamara@intel.com>,
jspewock@iol.unh.edu, "Juraj Linkeš" <juraj.linkes@pantheon.tech>,
khemendra.kumar13@gmail.com, konstantin.ananyev@intel.com,
"Kevin Traynor" <ktraynor@redhat.com>,
liang-min.wang@intel.com, "Lijuan Tu" <lijuan.tu@intel.com>,
lixuming@huawei.com, luca.boccassi@gmail.com,
"Lincoln Lavoie" <lylavoie@iol.unh.edu>,
malathi.malla@spirent.com, mallam@gmail.com,
marko.kovacevic@intel.com, matt.spencer@arm.com,
"Maxime Coquelin" <maxime.coquelin@redhat.com>,
msantana@redhat.com, nishant.lodha@cavium.com,
nlodha@marvell.com, "Owen Hilyard" <ohilyard@iol.unh.edu>,
"Matz, Olivier" <olivier.matz@6wind.com>,
piotr.zedlewski@intel.com, "Patrick Robb" <probb@iol.unh.edu>,
qian.q.xu@intel.com, "Ruifeng Wang" <ruifeng.wang@arm.com>,
scampbel@qti.qualcomm.com, scott.titus@intel.com,
shepard.siegel@atomicrules.com,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Arpit Joshipura" <tdelanerolle@linuxfoundation.org>,
"Thomas Monjalon" <thomas@monjalon.net>,
"O'Driscoll, Tim" <tim.odriscoll@intel.com>,
tomasz.zawadzki@intel.com, yu.y.liu@intel.com,
zhaoyan.chen@intel.com, zhoumin@loongson.cn
Subject: Reminder - DPDK Community CI Testing Meeting - Tomorrow 3/2/23 at
Date: Wed, 1 Mar 2023 18:11:26 -0500 [thread overview]
Message-ID: <CAKoDjhxHhN2nUQqt1Hs6wvO9t8K2UfQec8Jc-Ez+WXNUYi4Lsw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
Good evening,
Tomorrow, 2 Mar. 2023, the DPDK Project will hold its CI Community Testing
Meeting at 6am PT/9am ET/1400h GMT/1500h CET.
Zoom information to follow. We look forward to seeing you there.
Thanks,
Nathan
Nathan C. Southern, Project Coordinator
Data Plane Development Kit
The Linux Foundation
248.835.4812 (mobile)
nsouthern@linuxfoundation.org
Join Zoom Meeting
*https://zoom.us/j/95952696590?pwd=b0JjVnJaWDZ3TW1XYjZKQkxmZUZuQT09*
<https://www.google.com/url?q=https://zoom.us/j/95952696590?pwd%3Db0JjVnJaWDZ3TW1XYjZKQkxmZUZuQT09&sa=D&source=calendar&ust=1678143299018001&usg=AOvVaw0MoTGQ8-ENDwocLrqLw49x>
Meeting ID: 959 5269 6590
Password: 815823
One tap mobile
+16465588656,,95952696590#,,#,815823# US (New York)
+13126266799,,95952696590#,,#,815823# US (Chicago)
Dial by your location
+1 646 558 8656 US (New York)
+1 312 626 6799 US (Chicago)
+1 346 248 7799 US (Houston)
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US
+1 301 715 8592 US
855 880 1246 US Toll-free
877 369 0926 US Toll-free
+1 438 809 7799 Canada
+1 587 328 1099 Canada
+1 647 374 4685 Canada
+1 647 558 0588 Canada
+1 778 907 2071 Canada
855 703 8985 Canada Toll-free
Meeting ID: 959 5269 6590
Password: 815823
Find your local number: *https://zoom.us/u/aluff6iKE*
<https://www.google.com/url?q=https://zoom.us/u/aluff6iKE&sa=D&source=calendar&ust=1678143299018001&usg=AOvVaw2XSZ-bzfru0nDzi2YOESaw>
[-- Attachment #2: Type: text/html, Size: 10081 bytes --]
reply other threads:[~2023-03-01 23:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAKoDjhxHhN2nUQqt1Hs6wvO9t8K2UfQec8Jc-Ez+WXNUYi4Lsw@mail.gmail.com \
--to=nsouthern@linuxfoundation.org \
--cc=aconole@redhat.com \
--cc=ahassick@iol.unh.edu \
--cc=alialnu@mellanox.com \
--cc=aweltz@linuxfoundation.org \
--cc=blo@iol.unh.edu \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=chun.zhang@intel.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=erezsc@mellanox.com \
--cc=erezsc@nvidia.com \
--cc=ferruh.yigit@intel.com \
--cc=galco@mellanox.com \
--cc=galco@nvidia.com \
--cc=georgii.tkachuk@intel.com \
--cc=gurucode@gmail.com \
--cc=hemant.agrawal@nxp.com \
--cc=hnadeau@iol.unh.edu \
--cc=honnappa.nagarahalli@arm.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=john.mcnamara@intel.com \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=khemendra.kumar13@gmail.com \
--cc=konstantin.ananyev@intel.com \
--cc=ktraynor@redhat.com \
--cc=liang-min.wang@intel.com \
--cc=lijuan.tu@intel.com \
--cc=lixuming@huawei.com \
--cc=luca.boccassi@gmail.com \
--cc=lylavoie@iol.unh.edu \
--cc=malathi.malla@spirent.com \
--cc=mallam@gmail.com \
--cc=marko.kovacevic@intel.com \
--cc=matt.spencer@arm.com \
--cc=maxime.coquelin@redhat.com \
--cc=msantana@redhat.com \
--cc=nishant.lodha@cavium.com \
--cc=nlodha@marvell.com \
--cc=ohilyard@iol.unh.edu \
--cc=olivier.matz@6wind.com \
--cc=piotr.zedlewski@intel.com \
--cc=probb@iol.unh.edu \
--cc=qian.q.xu@intel.com \
--cc=ruifeng.wang@arm.com \
--cc=scampbel@qti.qualcomm.com \
--cc=scott.titus@intel.com \
--cc=shepard.siegel@atomicrules.com \
--cc=stephen@networkplumber.org \
--cc=tdelanerolle@linuxfoundation.org \
--cc=thomas@monjalon.net \
--cc=tim.odriscoll@intel.com \
--cc=tomasz.zawadzki@intel.com \
--cc=yu.y.liu@intel.com \
--cc=zhaoyan.chen@intel.com \
--cc=zhoumin@loongson.cn \
/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).