From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] next technical board meeting, 2017-03-20
Date: Fri, 17 Mar 2017 12:02:30 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772583FAD1311@IRSMSX109.ger.corp.intel.com> (raw)
Hello everyone,
A meeting of the DPDK technical board will occur next Monday,
March 20th 2017 at 3pm UTC.
The meeting takes place on the #dpdk-board channel on IRC.
This meeting is public, so anybody can join, see below for the agenda.
Konstantin
1. AVP PMD
Patches: http://dpdk.org/dev/patchwork/project/dpdk/list/?submitter=&state=&q=AVP&archive=&delegate=
Discussion: http://dpdk.org/ml/archives/dev/2017-March/060318.html
2. Failsafe PMD
Patches: http://dpdk.org/dev/patchwork/project/dpdk/list/?submitter=&state=&q=net%2Ffailsafe&archive=&delegate=
Discussion: http://dpdk.org/ml/archives/dev/2017-March/060272.html
3. PRGDEV PMD
Patches: http://dpdk.org/dev/patchwork/project/dpdk/list/?submitter=&state=&q=prgdev&archive=&delegate=
Discussion: http://dpdk.org/ml/archives/dev/2017-March/059604.html
4. Hierarchical QoS scheduler
Patches: http://dpdk.org/dev/patchwork/project/dpdk/list/?submitter=19&state=&q=&archive=&delegate=
Discussion: http://dpdk.org/ml/archives/dev/2017-March/059604.html
5. Community questions/issues
reply other threads:[~2017-03-17 12:02 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=2601191342CEEE43887BDE71AB9772583FAD1311@IRSMSX109.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
/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).