DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: dpdk-dev <dev@dpdk.org>, Aaron Conole <aconole@redhat.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	Lijuan Tu <lijuan.tu@intel.com>,
	 Juraj Linkeš <juraj.linkes@pantheon.tech>,
	Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: nd <nd@arm.com>, nd <nd@arm.com>
Subject: [dpdk-dev] DTS Workgroup: MoM 05/19/2021
Date: Wed, 26 May 2021 05:47:24 +0000
Message-ID: <DBAPR08MB58145B328EB7834B49F4002998249@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)


Aaron Conole

Honnappa Nagarahalli

Thomas Monjalon

Lijuan Tu

Juraj Linkes

Lincoln Lavoie

The meeting announcements are sent to dev@dpdk.org<mailto:dev@dpdk.org>.


Review action items from 5/12/2021

1) fm10K test cases can be removed. Intel DTS team will have a patch to remove them.

2) We need to provide time to the community to get feedback before making it mandatory. The tentative timeline end of 21.08  - release to developers and receive feedback till 21.11. Need time to fix any issues reported by developers. Make it mandatory after fixing the issues (time line will be decided depending on the issues)

3) Create a dts-next branch to start working on the issues we are identifying in this work group

4) In the future DTS will have a branch/tag for every DPDK release. Backporting rules will be the same as the ones followed for DPDK.
5) The work item related discussions are captured in [1]

Action items:

Honnappa - Validate test-pmd to make sure the mac-fwd printf statement output is available in 'show fwd stats'

Lijuan Tu - dts-next branch already exists. Merge the master to dts-next.

Juraj - 1) Create a list of test cases using sed scripts. Need to identify the work items from this list.

            2) Create a ticket in DTS Bugzilla to fix the IAVF enablement in the framework.

Thomas - Request LF to add a link on DTS bugs in the DTS links under hosted projects

[1] https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-qNvUb-fBdjA6DGusy4yM/edit?usp=sharing

                 reply	other threads:[~2021-05-26  5:47 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DBAPR08MB58145B328EB7834B49F4002998249@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=lijuan.tu@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=nd@arm.com \
    --cc=thomas@monjalon.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git