DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Brandon Lo <blo@iol.unh.edu>,
	Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	"juraj.linkes@pantheon.tech" <juraj.linkes@pantheon.tech>,
	Lijuan Tu <lijuan.tu@intel.com>,
	Owen Hilyard <ohilyard@iol.unh.edu>,
	Lincoln Lavoie <lylavoie@iol.unh.edu>,
	Aaron Conole <aconole@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>, nd <nd@arm.com>
Subject: [dpdk-dev] DTS Workgroup: MoM 08/03/2021
Date: Wed, 11 Aug 2021 03:40:45 +0000
Message-ID: <DBAPR08MB5814EE2117F412A24E3B87ED98F89@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)

Aaron Conole
Brandon Lo
Honnappa Nagarahalli
Juraj Linkes
Lijuan Tu
Owen Hilyard

The meeting announcements are sent to dev@dpdk.org.

1) Move DTS to follow standard python practices of organizing the project. This will be done after the 21.08 release. A write-up would be sent out to the community describing the change to ensure everyone is aware and can raise issues.
2) The work item related discussions are captured in [1]

Action Items:
1) Write a script that will output the testcases based on the files that are modified in the patch - Owen
2) Identify a set of test cases (based on the HW setup at Intel lab) to run for every patch - Lijuan
    The union of the test cases from above two action items will run as DTS CI.
3) Possibility of hosting the DTS CI at UNH - Owen and Lincoln
4a) Send out a write up to the community to move DTS to follow standard python project format - Owen
4b) Create a patch once there is conclusion in the community on Owen's proposal - Juraj

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

                 reply	other threads:[~2021-08-11  3:41 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=DBAPR08MB5814EE2117F412A24E3B87ED98F89@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=aconole@redhat.com \
    --cc=blo@iol.unh.edu \
    --cc=dev@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=lijuan.tu@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=nd@arm.com \
    --cc=ohilyard@iol.unh.edu \


* 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