From: Ferruh Yigit <ferruh.yigit@intel.com>
To: techboard@dpdk.org
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>, dpdk-dev <dev@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of September 26
Date: Thu, 27 Sep 2018 16:22:13 +0100 [thread overview]
Message-ID: <ffe2bfc6-102c-6529-b9d0-4db96fcb07e4@intel.com> (raw)
Meeting notes for the DPDK technical board meeting
held on 2018-09-26
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
0) Items from previous week
- security process
- Thomas & Maxime will contact Trishan about it
- website updates
- Thomas to write a draft and send it to marketing + techboard
1) Ask from Jeff about "hotplug failure handler" status
- Overall plan is do more review and merge in this release
- Thomas, Stephen, Ferruh planning to do reviews
- Stephen asks if there is a way to test hotplug without specialized hardware
- Thomas will send more hotplug patches for this release, please review
2) Opens
- rte_flow
- Ferruh, rte_flow patches are accumulated
- Can be good to have a backup maintainer to help Adrien
- Will ping for some interested developers
- Honnappa requested change 'ARM' to 'Arm' in website
- Honnappa will send request by email, to web mail list?
- For next techboard meeting:
- should we ask SPDK to merge in DPDK?
- rte_eth_dev_attach deprecated and replaced API rte_eal_hotplug_add is
experimental
- Consider removing experimental tag from these APIs
- Kevin, maybe deprecation should only happen when there is
non-experimental option available.
3) Recurring items
- SPDX
- Intel shared code drops gets SPDX updates
- Hemant is tracking the SPDX gaps
- meson
- With work by Luca and Bruce, Debian can use meson for DPDK packaging
4) Next techboard meeting
- It will be on October 10
- Hemant Agrawal will chair it
reply other threads:[~2018-09-27 15:22 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=ffe2bfc6-102c-6529-b9d0-4db96fcb07e4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=techboard@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).