DPDK CI discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: dpdk-dev <dev@dpdk.org>, "ci@dpdk.org" <ci@dpdk.org>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	David Marchand <david.marchand@redhat.com>
Cc: "Aaron Conole" <aconole@redhat.com>,
	"Ali Alnubani" <alialnu@nvidia.com>,
	"Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
	"Owen Hilyard" <ohilyard@iol.unh.edu>,
	"Tu, Lijuan" <lijuan.tu@intel.com>,
	"Ajit Khaparde (ajit.khaparde@broadcom.com)"
	<ajit.khaparde@broadcom.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"David Liu" <dliu@iol.unh.edu>,
	"Lincoln Lavoie" <lylavoie@iol.unh.edu>,
	"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
	"jerinj@marvell.com" <jerinj@marvell.com>, nd <nd@arm.com>,
	"Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>,
	nd <nd@arm.com>
Subject: [dpdk-ci] DTS improvement working group - MoM
Date: Tue, 13 Apr 2021 22:35:17 +0000	[thread overview]
Message-ID: <DBAPR08MB5814DA41F598E25F5F4C6BA2984F9@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)

Hello,
	Thanks to many of you for attending the meeting today. Following are the MoM.

Attendees:
Aaron Conole
Ajit Khaparde
Ali Alnubani
Bruce Richardson
David Liu
Honnappa Nagarahalli
Jerin Jacob Kollanukkaran
John McNamara
Juraj Linkes
Konstantin Ananyev
Lijuan Tu
Lincoln Lavoie
Owen Hilyard
Zhaoyan Chen
(I have missed few)

Minutes:
1) This work group is created with the intention to improve DTS to make it easy to add new test cases by the community. The intention is to make it mandatory to submit test cases to DTS whenever new features are added to PMDs.
2) Agreed on following 3 steps
	a) Collect feedback as much as possible at this point.
	b) Debate and triage the work items.
	c) Create Bugzilla tickets with some timelines in mind.
3) Agreed on 2 weeks' time period to complete step 2a above. The next meeting will be on 28th April. This will help make progress quickly rather than spending time collecting a lot of inputs.
4) Following are the leads who will work with their respective teams to complete step 2a above.
	Ajit - Broadcom
	Ali - Mellanox	
	Honnappa - Arm
	Jerin - Marvell
	Lijuan Tu/Zhaoyan Chen - Intel
	Lincoln - UNH
    Having said this, anyone from the community can provide inputs. Please add your inputs to [1].

Thank you,
Honnappa


[1] https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-qNvUb-fBdjA6DGusy4yM/edit#

	

                 reply	other threads:[~2021-04-13 22:35 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=DBAPR08MB5814DA41F598E25F5F4C6BA2984F9@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=aconole@redhat.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=alialnu@nvidia.com \
    --cc=bruce.richardson@intel.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dliu@iol.unh.edu \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=juraj.linkes@pantheon.tech \
    --cc=konstantin.ananyev@intel.com \
    --cc=lijuan.tu@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=nd@arm.com \
    --cc=ohilyard@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --cc=zhaoyan.chen@intel.com \
    /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).